10798 2010-09-28 22:46:15 +0000 [Selection] Find a new home for Selection 2011-08-04 05:00:30 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED P3 normal --- 11017 10583 9514 10624 10691 1 ian ian annevk former-z^corpan ian mike mjs Ms2ger public-html-admin public-html-wg-issue-tracking public-webapps timdown public-html-bugzilla oldest_to_newest 39823 0 ian 2010-09-28 22:46:15 +0000 We should probably move Selection into the new DOM Range spec. 39967 1 Ms2ger 2010-09-29 15:18:04 +0000 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…) 40002 2 ian 2010-09-29 19:35:28 +0000 I think innerText needs to be in CSSOM, since it depends on CSS a lot as I understand it. 40004 3 ian 2010-09-29 19:42:07 +0000 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. 40136 4 mike 2010-09-30 10:47:26 +0000 (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: http://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG http://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&component=DOM%20Range 40463 5 Ms2ger 2010-10-01 20:10:43 +0000 http://bitbucket.org/ms2ger/dom-range/changeset/d853f2cbb7f6 40652 6 Ms2ger 2010-10-05 18:33:53 +0000 Actually, this still needs to go from HTML, I guess. 40995 7 ian 2010-10-12 07:39:17 +0000 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.) 41091 8 Ms2ger 2010-10-12 12:15:17 +0000 http://bitbucket.org/ms2ger/dom-range/changeset/d853f2cbb7f6/raw/dom-range-d853f2cbb7f6.diff 41104 9 timdown 2010-10-12 13:40:14 +0000 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. 41157 10 ian 2010-10-12 18:41:35 +0000 I'm sure nothing's off limits. :-) 41176 11 ian 2010-10-12 21:44:32 +0000 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: see diff given below Rationale: I've removed Selection from HTML. Thanks Ms2er. I'll reassign the relevant bugs to the Range component. 41177 12 ian 2010-10-12 21:45:14 +0000 Checked in as WHATWG revision r5617. Check-in comment: Move Selection to DOM Range. http://html5.org/tools/web-apps-tracker?from=5616&to=5617 52341 13 mike 2011-08-04 05:00:30 +0000 mass-moved component to LC1