Sad day for web standards
Tuesday, 22. January 2008, 15:30:37
A blog about Web Development, Web Standards, Opera, and Related Pleasantries
As mentioned, Firefox does not support SVG as CSS background yet ...
anonymous
AJL writes: This does not appear to work for firefox 3.0.5. It ...
anonymous
RaphielDrake writes: but its not even as if its just how few go ...
Hello!This widget is fantastic. I really love this one. But the ...
anonymous
My country --Taiwan writes: eduMap widget is good!:up: But....T ...
Anonymous # 23. January 2008, 22:10
Winners: forward-thinking web developers (because Microsoft can make changes to the engine without fearing to "break the web" (at least for a while), so developers can use new technology in IE sooner) and lazy web developers
Losers: Alternate browsers (maybe) and Microsoft (because it's hard to have multiple engines in the same product, as outlined by Robert O'Callahan and others)
jeff_schiller # 14. February 2008, 21:40
Bear in mind that Chris Wilson has stated that IE will also switch into "super standards" mode when it encounters DOCTYPEs that aren't widely deployed (he explicitly mentioned HTML5, but who knows - maybe XHTML too?)
Fyrd # 18. February 2008, 16:44
And yes, the HTML5 DOCTYPE news could be a good thing (I personally am ready to start using HTML5 the moment it's stable/supported well enough), but I worry that
MS might just find themselves having the same kind of problem they do now in the future when many sites have HTML5 DOCTYPEs but still include workarounds to IE bugs. This would be similar to the feared situation of everyone just using IE=edge (which the ALA article states is actually "strongly discouraged").
Jeff, you're more optimistic about IE's XHTML support than I am. But then I wasn't expecting Acid2 support in IE8 either, so who knows.
jeff_schiller # 19. February 2008, 17:41
Even if they don't support SVG in IE8, I don't see any reason for them not to support XHTML, XML parsers are a dime-a-dozen these days.