Falling back, or falling down...
Monday, 21. April 2008, 20:11:22
Microsoft tries to improve web standards support in IE8 apparently...well, except for...
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
Source: IE8BlogKnown issues we are not planning to change in IE8
- <OBJECT> 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.
- <OBJECT> 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.
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
WIDGETIZE
dahulevogyre # 30. April 2008, 13:46
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.