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 10798 - [Selection] Find a new home for Selection
Summary: [Selection] Find a new home for Selection
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on: 11017
Blocks: 10583 9514 10624 10691
  Show dependency treegraph
Reported: 2010-09-28 22:46 UTC by Ian 'Hixie' Hickson
Modified: 2011-08-04 05:00 UTC (History)
10 users (show)

See Also:


Description Ian 'Hixie' Hickson 2010-09-28 22:46:15 UTC
We should probably move Selection into the new DOM Range spec.
Comment 1 Ms2ger 2010-09-29 15:18:04 UTC
I can do that, but I am not planning to put a lot of work in that spec. (And I'm certainly not planning to spec innerText…)
Comment 2 Ian 'Hixie' Hickson 2010-09-29 19:35:28 UTC
I think innerText needs to be in CSSOM, since it depends on CSS a lot as I understand it.
Comment 3 Ian 'Hixie' Hickson 2010-09-29 19:42:07 UTC
Ms2ger: Ok let's yank Selection from HTML and move it to Range. Should I just extract all the spec source material on this and attach it to this bug?

Mike: Is there a bug component Web DOM Range, and if not, can we create one?

FWIW, I'm not really worried about who specs Range. When I finally get around to working on execCommand again and the rest of contentEditable, I'll need Range, so if it doesn't have an editor at that point I can take over. I'm punting on that for a while though, need to get the stuff we have written so far sorted out and ready to go. Having everything Range-related in one place (like Selection) makes getting the rest of the stuff ready sooner easier.
Comment 4 Michael[tm] Smith 2010-09-30 10:47:26 UTC
(In reply to comment #3)
> Mike: Is there a bug component Web DOM Range, and if not, can we create one?

added as a new component in WebApps WG product:
Comment 6 Ms2ger 2010-10-05 18:33:53 UTC
Actually, this still needs to go from HTML, I guess.
Comment 7 Ian 'Hixie' Hickson 2010-10-12 07:39:17 UTC
Do you have a link to the actual spec so that I can see what I should remove? (Or even better, to the diff of what you changed... the URL you gave doesn't include the relevant diff.)
Comment 9 Tim Down 2010-10-12 13:40:14 UTC
I am planning to do some work on this spec since I feel I can contribute. I have meant to start doing so sooner but I've been rather busy. If any parts are more urgent or off limits then please tell me. I'm hoping to start doing a little work on it later today.
Comment 10 Ian 'Hixie' Hickson 2010-10-12 18:41:35 UTC
I'm sure nothing's off limits. :-)
Comment 11 Ian 'Hixie' Hickson 2010-10-12 21:44:32 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:

Status: Accepted
Change Description: see diff given below
Rationale: I've removed Selection from HTML.

Thanks Ms2er. I'll reassign the relevant bugs to the Range component.
Comment 12 Ian 'Hixie' Hickson 2010-10-12 21:45:14 UTC
Checked in as WHATWG revision r5617.
Check-in comment: Move Selection to DOM Range.
Comment 13 Michael[tm] Smith 2011-08-04 05:00:30 UTC
mass-moved component to LC1