Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by melito | Hacker News Reader

Parent Full thread

melito·

So uh, does this kill browser targeting?

http://www.alistapart.com/articles/beyonddoctype

Or can you just do something like content="IE=8;chrome=1" ?

View on HN

Looks like you can target the user agent:

"Google Chrome Frame reports that it is available by extending the host's User-Agent header to add the string chromeframe. You can use server-side detection to look for this token and determine whether Google Chrome Frame can be used for a page. If Google Chrome Frame is present, you can insert the required meta tag; if not, you can redirect users to a page that explains how to install Google Chrome Frame."

http://code.google.com/chrome/chromeframe/developers_guide.h...

Oh boy. Another browser to support. Thanks Google!

Don't support browsers, support standards!

Isn't a valid part of "supporting standards" declining to support what ignores standards?

Yes, but you have to pick your battles. Unless you run an already ginormously successful site which can afford a substantial loss of traffic, then being dogmatic about web standards will only hurt you and do nothing to drive people away from non-standards compliant browsers.

... not sure anything is likely to drive people away from standards compliant browsers, maybe just sites that won't render in less capable browsers.

I reckon the user would blame a poorly rendered site on the author/owner rather than the browser.

Standards are the goal, and it's never been closer. However, interoperability is more important. Writing markup, code and styles to the standards and provide at least an accessible level of operability to the less capable user agents.

It's the same version of Webkit ued in standard chrom, according to the article. If you're already supporting chrome, it should only take one more line of html to support chromeframe.

Reply on news.ycombinator.com