13593 2011-08-03 06:42:03 +0000 Let drag and drop sources and targets register supported formats 2011-08-14 06:14:47 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WORKSFORME a11y, a11ytf P2 normal --- 1 gcl-0039 ian ian jackalmage laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52117 0 gcl-0039 2011-08-03 06:42:03 +0000 HTML5 should allow drag and drop sources and targets to register which formats they support. Use case: Janis is using the keyboard to move items in a Web application. There are a hundred icons functioning as drag sources and targets, not all of which support the same data types. She wants to drag an icon representing a User onto one representing a Group or Office. She navigates to the icon and chooses the Drag command from its shortcut menu. At this point, a browser add-on highlights only those icons representing appropriate drag targets (those supporting the user data type). The add-on could also create temporary keyboard shortcuts for just those compatible targets or even present them as a drop-down list, which would make the operation much more efficient than if Janis had to navigate through a dozens of icons to reach her goal, more closely approximating the ease and efficiency available to mouse users. Note: See bug 13591 for a discussion of why drag and drop is valuable for accessibility. 52177 1 jackalmage 2011-08-03 15:11:52 +0000 The @dropzone attribute already does precisely this. 53439 2 mike 2011-08-04 05:13:54 +0000 mass-move component to LC1 54916 3 ian 2011-08-14 06:14:47 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: no spec change Rationale: This seems to have been fixed already.