HTML 5 is a mess. Now what? A few days ago on this site, John Allsopp argued passionately that HTML 5 is a mess. In response to HTML 5 activity leader Ian Hickson’s comment here that, “We don’t need to predict the future. When the future comes, we can just fix HTML again,” Allsopp said “This is the only shot for a generation” to get the next version of markup right. Now Bruce Lawson explains just why HTML 5 is “several different kind of messes:” It’s a mess, Lawson says, because the process is a mess. The process is a mess, he claims, because “[s]pecifying HTML 5 is probably the most open process the W3C has ever had,” and when you throw open the windows and doors to let in the fresh air of community opinion, you also invite sub-groups with different agendas to create competing variant specs. Damned if you do The third point is Lawson’s key insight, for it illuminates the dilemma faced by HTML 5 or any other honest effort to move markup forward.
XHTML 2 was conceived as an effort to start over and get it right. Coding A HTML 5 Layout From Scratch. Advertisement HTML5 and CSS3 have just arrived (kinda), and with them a whole new battle for the ‘best markup’ trophy has begun. Truth to be told, all these technologies are mere tools waiting for a skilled developer to work on the right project. As developers we shouldn’t get into pointless discussions of which markup is the best. They all lead to nowhere. While it is true HTML5 and CSS3 are both a work in progress and is going to stay that way for some time, there’s no reason not to start using it right now. So today we’re going to experiment a little with these new technologies. Use Graceful Degradation techniques and technologies to keep things in place for legacy browsers.Use Progressive Enhancement techniques and technologies to be up to date with the latest trends.Use HTML5 alongside a rising technology: Microformats.Have a clear vision of some of the most exciting new features HTML5 and CSS3 will bring.
It’d be a good idea to have a read at some of these articles first: 1. 2. <! <! HTML5 Drag and Drop in deeetail. Friday, July 17th, 2009 <p>Les Orchard isn’t just a cool domain name. He is a person. A person who has done a great job detailing HTML 5 drag and drop that you can use today in Firefox 3.5. Les takes us down the path from simple drag and drop, to event propagation, to feedback images, to rich data transfer information all with great demos: It is so cool to be able to do things like this: var dt = ev.originalEvent.dataTransfer; dt.setDragImage( $('#feedback_image h2')[0], 0, 0);dt.setDragImage( $('#logo')[0], 32, 32); var canvas = document.createElement("canvas");canvas.width = canvas.height = 50;var ctx = canvas.getContext("2d");ctx.lineWidth = 8;ctx.moveTo(25,0);ctx.lineTo(50, 50);ctx.lineTo(0, 50);ctx.lineTo(25, 0);ctx.stroke();dt.setDragImage(canvas, 25, 25); Drag and drop on the Web has always been a strange beast, but at least now we have a rich API…. so maybe it will get a revival?
HTML Drag and Drop. HTML5 drag and drop in Firefox 3.5 Oh hey, look! It's another blog post—and this one is cross-posted on hacks.mozilla.com. I won't say this is the start of a renewed blogging habit, but let's see what happens. Drag and drop is one of the most fundamental interactions afforded by graphical user interfaces. In one gesture, it allows users to pair the selection of an object with the execution of an action, often including a second object in the operation.
It's a simple yet powerful UI concept used to support copying, list reordering, deletion (ala the Trash / Recycle Bin), and even the creation of link relationships. Since it's so fundamental, offering drag and drop in web applications has been a no-brainer ever since browsers first offered mouse events in DHTML. Of course, that doesn't prevent most modern JavaScript frameworks from abstracting away most of the problems and throwing in some flourishes while they're at it.
The New Drag and Drop Events dragstart drag dragenter dragover dragleave all. HTML 5. B.3 Acknowledgments This section is non-normative. At the time of publication, the members of the RDF Web Applications Working Group were: Ivan Herman (staff contact), Shane McCarron, Gregg Kellogg, Niklas Lindström, Knud Möller, Steven Pemberton, Manu Sporny (chair), Stéphane Corlosquet and Thomas Steiner. At the time of publication, the members of the HTML Working Group were: