Falling back, or falling down...
Monday, April 21, 2008 8:11:22 PM
ie8 , standards
Microsoft tries to improve web standards support in IE8 apparently...well, except for...
Known issues we are not planning to change in IE8
is not parsed in a cross-browser compatible way (parsing stops at the OBJECT, whereas other browsers continue parsing all the fallback content and make it available. No support for this parsing behavior is planned for IE8; I'll take this opportunity to ask for real-world scenarios that can help me prioritize this feature.
elements cannot be 'reactivated' by dynamically correcting the attributes that caused the original fallback. Again, your feedback on the potential benefits/use-cases for this feature appreciated.
Source:
IE8Blog Being web standards compliant is not important enough?
Anyway, in practice it means that IE users won't be able to see most graphics on my blog. I usually provide some kind of fallback content for the
tags I use. This makes it easier to do progressive enhancement, browsers that don't handle some type of content at all get some other content to munge on instead. Or anyway, that was the thought.
dahulevogyre # Wednesday, April 30, 2008 1:46:24 PM
Doesn't the first point actually mean the fallback DOM fragment will not be there for objects that DON'T fall back ?
The post talks about fallback mechanism actually implemented.