Hi, and what about adding drag 'n drop "on Element level" not "Widget level"? maybe it is even more crucial. As marking element to be draggable int html5 is made by adding attribute to dom node, drag-ability seems to be transitive. So maybe it's reasonable to implement drag n drop features not directly on element but on sth that wraps element, sets draggable property and has a bunch of methods for common drag'n'drop-related activities?
and last but surely not least: maybe it would be a good solution to implement HTML5 features support as pair of interfaces and implementation classes to allow fallback classes to implement the same interfaces. btw. this last remark applies to all HTML5 features - and maybe is worth to be more exposed to discussion in its own thread :). -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
