[Bug 7721] Drag and Drop is not keyboard accessible

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7721


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WORKSFORME




--- Comment #8 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-10-18 10:20:31 ---
(In reply to comment #7)
> The problem you seem to be missing is that to keyboard enable the functions I
> am suggesting the author needs to write their own script methods to reproduce
> the functionality.

No, this is incorrect. The browser can support keyboard-based drag and drop.
There's nothing in HTML5 that implies the user agent has to have mouse support
to do drag and drop. It doesn't even require a visual media UA -- you could
implement drag and drop in a speech browser, and still be compliant per the
HTML5 spec.


> For example, to do a setDragImage I cannot use the standard
> function that is provided ONLY in MOUSE events.

I have no idea what you mean here. setDragImage() is available on the
'dragstart' event, which is a DragEvent, not a MouseEvent. It fires
irrespective of the input device used to trigger drag and drop. That's entirely
up to the UA. It could be triggered by foot pedal, that would be just as
spec-compliant.


> What I want to see is for the HTML 5 specification provide equivalent support
> to developers who need to support keyboard drag and drop.

The drag and drop feature is media- and device- independent.


> There should be a standard handler that gets triggered (without using the
> mouse) to notify a developer that the author has selected items for drag (the

I assume you mean user here, not author.

> user agent can define the key sequence) without the author having to write
> extra script. 

There is. All the events in the drag and drop model work like this.


> If you think these are addressed point to me where and how in the specification
> this is possible. Nowhere in the spec does it show how this functionality be
> exposed to the keyboard user.

Nowhere in the the spec does it show how this functionality is exposed to the
mouse user either. The spec is input-device agnostic. It allows the user agent
to implement the interface however it likes.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 18 October 2009 10:20:33 UTC