Comments on: IE8 opt-in: no problem after all? http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/?utm_source=rss&utm_medium=rss&utm_campaign=ie8-opt-in-no-problem-after-all Thoughts on web development and technologies by Peter Gasston Thu, 29 Jul 2010 15:25:08 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Stifu http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/#comment-6982 Stifu Sun, 27 Jan 2008 21:28:15 +0000 http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/#comment-6982 I forgot to state something important: XHTML support still hasn't been confirmed in IE8 yet. (But I think they'll add it) Anyway, what I said above should still work whenever IE supports XHTML, whether it is in version 8 or later... I forgot to state something important: XHTML support still hasn’t been confirmed in IE8 yet. (But I think they’ll add it)
Anyway, what I said above should still work whenever IE supports XHTML, whether it is in version 8 or later…

]]> By: Stifu http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/#comment-6979 Stifu Sun, 27 Jan 2008 21:19:21 +0000 http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/#comment-6979 Apparently, the same will go for pages served as "application/xhtml+xml". That means that as an alternative, we could use a conditional comment to serve pages as "text/html" to IE<=7, and serve "application/xhtml+xml" to every other browser. Apparently, the same will go for pages served as “application/xhtml+xml”. That means that as an alternative, we could use a conditional comment to serve pages as “text/html” to IE<=7, and serve “application/xhtml+xml” to every other browser.

]]> By: Robin http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/#comment-6881 Robin Fri, 25 Jan 2008 11:23:35 +0000 http://www.broken-links.com/2008/01/24/ie8-opt-in-no-problem-after-all/#comment-6881 Well, the problem is that (as you say) it's still too early to start using HTML5 on production sites for customers. The spec's by no means finalised even if we do have a working draft. Having said that, for personal sites this is fine, and certainly better than the alternative of browser-specific cruft. Well, the problem is that (as you say) it’s still too early to start using HTML5 on production sites for customers. The spec’s by no means finalised even if we do have a working draft.

Having said that, for personal sites this is fine, and certainly better than the alternative of browser-specific cruft.

]]>