One of the guiding principles of HTML5 and its WHAT-WG precursors is to document everything that already works in browsers but previous Working Groups couldn’t be arsed to specify, such as innerHTML and offsetWidth.Īlthough I thoroughly support that principle and see how it applies to the Microsoft drag and drop module, I still think that some form of critical reflection might have been in order in this particular case. Still, while Microsoft is to blame initially, the HTML5 WG and the other browser vendors are accessories to the crime. This specification was terribly bad, as we’ll see in a moment. Microsoft “designed” and implemented drag and drop way back in 1999, when IE 5.0 was released. What follows is a rant laced with profanity. I refuse to do any more research on drag and drop. In fact, it’s so outrageously bad that I’ve gone on strike. Exactly because the spec has such an overall quality I was so surprised (and, frankly, a bit confused and hurt) to find drag and drop a steaming pile of bovine manure. They should use old-school scripts instead.īefore we continue I’d like to say that in general I thoroughly approve of the HTML5 specification. Web developers MUST NOT (in the sense of RFC 2119) use HTML 5 drag and drop. The module should be removed from the HTML5 specification straight away, and conforming browsers should disable it at their earliest opportunity pending a complete rewrite from the ground up. Sitemap contact The HTML5 drag and drop disasterĪfter spending about a day and a half in testing I am forced to conclude that the HTML5 drag and drop module is not just a disaster, it’s a fucking disaster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |