This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13593 - Let drag and drop sources and targets register supported formats
Summary: Let drag and drop sources and targets register supported formats
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf
Depends on:
Blocks:
 
Reported: 2011-08-03 06:42 UTC by Greg Lowney
Modified: 2011-08-14 06:14 UTC (History)
7 users (show)

See Also:


Attachments

Description Greg Lowney 2011-08-03 06:42:03 UTC
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.
Comment 1 Tab Atkins Jr. 2011-08-03 15:11:52 UTC
The @dropzone attribute already does precisely this.
Comment 2 Michael[tm] Smith 2011-08-04 05:13:54 UTC
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-14 06:14:47 UTC
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.