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 13911 - Active range's definition relies on the "context object" but there might not be one
Summary: Active range's definition relies on the "context object" but there might not ...
Status: NEW
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - HTML Editing APIs (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Deadline: 2015-07-30
Assignee: Aryeh Gregor
QA Contact: HTML Editing APIs spec bugbot
Depends on:
Reported: 2011-08-26 00:15 UTC by Ian 'Hixie' Hickson
Modified: 2015-07-30 23:47 UTC (History)
2 users (show)

See Also:


Description Ian 'Hixie' Hickson 2011-08-26 00:15:06 UTC
"context object" is defined as "the object on which the method or attribute being discussed was called".

"active range" is defined as "The active range is the first range in the Selection given by calling getSelection() on the context object". However, in the context of the definition of "active range", there isn't a method or attribute being discussed, so the term "context object" is undefined.

If we assume that the definition of "context object" is to be inherited from wherever the term "active range" is defined, then this fails in the case of the "Additional Requirements" section, where user interaction results in calling algorithms that rely on the active range, despite no method or attribute being involved at all at any point.
Comment 1 Aryeh Gregor 2011-08-28 15:45:06 UTC
Yeah, I've been really lazy with the use of "context object".  Really I always mean "current document", loosely speaking, but I have to be more precise here.