20004 2012-11-19 10:19:21 +0000 Maybe DataTransfer should have a constructor, for use with synthetic events. If there are no use cases for synthetic drag events, maybe drop the DragEvent constructor instead? 2013-03-06 20:51:51 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#datatransfer P3 normal Unsorted 1 contributor ian annevk ian mike contributor oldest_to_newest 78461 0 contributor 2012-11-19 10:19:21 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html Multipage: http://www.whatwg.org/C#datatransfer Complete: http://www.whatwg.org/c#datatransfer Comment: Maybe DataTransfer should have a constructor, for use with synthetic events. If there are no use cases for synthetic drag events, maybe drop the DragEvent constructor instead? Posted from: 81.231.170.159 User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.4) Presto/2.12.388 Version/12.10 84036 1 ian 2013-03-06 20:49:55 +0000 Creating a DataTransfer object is rather complicated because to make that object work the browser has to do magic in the background, deeply embedded in the way drag events fire. The DragEvent constructor is there just for consistency with other interfaces. It's not useful, but I don't know if it's more confusing to remove it or keep it. I've added a note to this effect. 84038 2 contributor 2013-03-06 20:51:51 +0000 Checked in as WHATWG revision r7735. Check-in comment: Point out that the constructor isn't really useful here. http://html5.org/tools/web-apps-tracker?from=7734&to=7735