Comments on: Microsoft's Acid (2) Reflux… http://thecrumb.com/2008/01/23/microsofts-acid-2-reflux/ developer | thinker | tinkerer Mon, 06 Feb 2012 15:30:25 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jim http://thecrumb.com/2008/01/23/microsofts-acid-2-reflux/#comment-606 Jim Wed, 23 Jan 2008 16:39:18 +0000 http://www.thecrumb.com/2008/01/23/microsofts-acid-2-reflux/#comment-606 @Rob - I agree completely. 'Standard' mode should be the default. Any 'fallback' mode should be optional. If you have an old site add the tag to 'fix' your site, if you build a standards compliant site no tag required. @Rob – I agree completely. ‘Standard’ mode should be the default. Any ‘fallback’ mode should be optional. If you have an old site add the tag to ‘fix’ your site, if you build a standards compliant site no tag required.

]]> By: Rob Wilkerson http://thecrumb.com/2008/01/23/microsofts-acid-2-reflux/#comment-605 Rob Wilkerson Wed, 23 Jan 2008 16:30:39 +0000 http://www.thecrumb.com/2008/01/23/microsofts-acid-2-reflux/#comment-605 There's a lot of debate about this from a lot of the big players (Meyer, Zeldman, Resig, et al). It requires more thought on my part, but at a glance I'd have to say that I think I'm okay with the mechanism, but the implementation is backwards. I understand "not breaking the web", but it should be more than that. It should be something more along the lines of "progress the web with the option to stand still". In other words, make progression (no meta tag) the default stand and backwards compatibility the opt-in. As I said it requires more thought (and more reading of folks who are closer to this that I am), but that's what I'm thinking at the moment. There’s a lot of debate about this from a lot of the big players (Meyer, Zeldman, Resig, et al). It requires more thought on my part, but at a glance I’d have to say that I think I’m okay with the mechanism, but the implementation is backwards.

I understand “not breaking the web”, but it should be more than that. It should be something more along the lines of “progress the web with the option to stand still”. In other words, make progression (no meta tag) the default stand and backwards compatibility the opt-in.

As I said it requires more thought (and more reading of folks who are closer to this that I am), but that’s what I’m thinking at the moment.

]]>