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 9514 - [Selection] Specify Selection.modify()
Summary: [Selection] Specify Selection.modify()
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Selection API (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ryosuke Niwa
QA Contact: public-webapps-bugzilla
URL:
Whiteboard: editing
Keywords: NE
: 24085 (view as bug list)
Depends on: 10798
Blocks:
  Show dependency tree / graph
 
Reported: 2010-04-14 11:32 UTC by contributor
Modified: 2016-04-11 07:39 UTC (History)
11 users (show)

See Also:

Attachments

Description contributor 2010-04-14 11:32:58 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#documentSelection

Comment:
Specify Selection.modify()

Posted from: 81.245.229.199 by ms2ger@gmail.com
Comment 3 Ms2ger 2010-04-15 19:48:50 UTC 
> [09:14] <Hixie> i am so not looking forward to working out how Selection.modify() works

I'm sorry, I just thought it was better to have it specified before a third incompatible implementation came about.
Comment 4 Ian 'Hixie' Hickson 2010-09-10 01:50:27 UTC 
Doing this properly probably needs DOM Range to be respecified first.

In fact, we should probably move all of the Selection interface to DOM Range.
Comment 5 Ian 'Hixie' Hickson 2010-09-26 20:01:41 UTC 
ms2ger: Can we put Selection in your DOM Range spec?
Comment 6 Aryeh Gregor 2011-01-28 18:52:19 UTC 
Working on this now.
Comment 7 Aryeh Gregor 2011-09-22 19:31:01 UTC 
Moving Selection-related bugs to editing: see bug 14248, bug 14252.
Comment 8 Aryeh Gregor 2014-02-19 12:42:39 UTC 
*** Bug 24085 has been marked as a duplicate of this bug. ***
Comment 9 Ben Peters 2014-04-21 19:35:56 UTC 
Moving to Selection API component.
Comment 10 Ryosuke Niwa 2016-04-11 07:39:08 UTC 
This is now tracked by https://github.com/w3c/selection-api/issues/37.