I can't speak to all of them, but for a few of your problems, the spec
was developed independently by Microsoft for use in IE, and is not a
standard. You can't expect other browser vendors to support every
random thing MS decides to stick in their browsers. That's why we
have web standards. If you're aiming for a cross-browser application,
I would recommend sticking to those standards.
True, if you want to have a cross-browser application, you either need
to stick to lowest common denominator or have something that degrades
nicely. Later usually can be done relatively cleanly.
However, saying this is a Microsoft problem isn't fair either. A lot of
HTML was developed in exactly the same way, by someone implementing a
feature outside of a standard that later others found useful. Even
Apple did it a year ago with type="search" attribute for input tag and
we'd certainly be without XMLHttpRequest, if followed only existing
standards.
I do agree that it could and should be better documented.
My personal pet peeve is when object detection fails because browser
lies and Safari was definitely guilty of this. It forces you to choose
a lesser evil, browser sniffing or broken degradation.
Regards,
Marko
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Web-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/web-dev/email@hidden
