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 15212 - If a text selection is identified for a drag operation
Summary: If a text selection is identified for a drag operation
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2011-12-15 15:50 UTC by John Foliot
Modified: 2012-01-29 12:10 UTC (History)
6 users (show)

See Also:

Attachments

Description John Foliot 2011-12-15 15:50:04 UTC 
If a text selection is identified  for a drag operation, is it identified as such in the DOM? If yes, how? (i.e. is there a 'getter' and 'setter'?) This is important for the AAPIs as normally individual text (as opposed to an element) is not tab focusable.
Comment 1 Ian 'Hixie' Hickson 2012-01-28 22:03:02 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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate?
Comment 2 Everett Zufelt 2012-01-29 12:10:42 UTC 
I believe that John is asking if there is a method of saving the state of a text selection in the DOM. This is related to ensuring that it is possible to make drag and drop of text selections accessible for users of assistive technology.

Is there a way to mark, in the DOM, the beginning, end, and direction, of a text selection, or is this something that UAs are expected to figure out on their own? If UAs must do this on their own, then this can cause problems, as ATs will need to interface with the UAs methods for text selection, rather than interacting with the DOM.