News for hackers. Stuff that matters.
Re:The Pain of HTML5 by azylman on Monday July 16, 2012 @01:42PM (#4251701)
I don't think "Best viewed in X" is a problem when you're trying to force people to use standards-compliant, modern browsers.

What made it a problem in the past is that people would rely on weird, kludgy, non-standard behavior of Browser X and slap on a "Best viewed in X".

Re:The Pain of HTML5 by azakai on Monday July 16, 2012 @02:53PM (#4251952)
But it sounds like this is exactly like those kludges.

Instead of detecting which browser the user has and saying "best viewed in X" where X is some other browser, how about detecting which features you need, and then giving a clear error on which were missing? This is better in many ways, for example if the next update to a browser adds the missing features to it, then it will just work on your site.

Re:The Pain of HTML5 by tomjen3 on Monday July 16, 2012 @03:25PM (#4252097)
That would confuse our users when there is no reason to.
Re:The Pain of HTML5 by azakai on Tuesday July 17, 2012 @01:05PM (#4256643)
What would confuse them? You can customize the warning message to be as clear as you want. The benefit your users get is your page will actually work the second their browser can support it, not when you officially define browser X to be "acceptable".