W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 13911] New: Active range's definition relies on the "context object" but there might not be one

From: <bugzilla@jessica.w3.org>
Date: Fri, 26 Aug 2011 00:15:06 +0000
To: public-webapps@w3.org
Message-ID: <bug-13911-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13911

           Summary: Active range's definition relies on the "context
                    object" but there might not be one
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML Editing APIs
        AssignedTo: ayg@aryeh.name
        ReportedBy: ian@hixie.ch
         QAContact: sideshowbarker+html-editing-api@gmail.com
                CC: mike@w3.org, public-webapps@w3.org


"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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 26 August 2011 00:15:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT