Hi Ian, firstly thanks for your comments.
--- Ian Hickson <i...@hixie.ch> wrote on Tuesday, 28. July 2009: > Whether draggable elements can be focused or not is up to > the user agent. > It's much like links -- in some browsers, whether they are > focusable or > not depends on the operating system accessibility > preferences. I agree. It's the same case here. Just like with "'a' elements that have an href attribute" we should also add "elements that have a draggable attribute set to true" to the list of elements that "should be made focusable by the user agent" at the bottom of section 7.5.1 of the spec. Btw. there is no information on what criteria the qualification is made for the elements in that "should" list in the spec. Maybe that should be added as well. > The user agent can actually find where drops can occur by > just acting as > if the user had tried to drop everywhere. I'm not really > sure how we could > make an attribute work for this, since the model allows any > element to be > a drop target already. Fair enough. I thought it might come in handy some day to identify both draggable elements as well as elements that can "receive" drops without the use of scripting. E.g. in a parser or for search spiders to creater indexes for that faster... Aron
