W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2012

[Bug 15583] New: BAD_BOUNDARYPOINTS_ERR no longer used for Range

From: <bugzilla@jessica.w3.org>
Date: Mon, 16 Jan 2012 12:12:04 +0000
To: www-dom@w3.org
Message-ID: <bug-15583-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15583

           Summary: BAD_BOUNDARYPOINTS_ERR no longer used for Range
           Product: WebAppsWG
           Version: unspecified
          Platform: All
               URL: http://w3c-test.org/webapps/DOMCore/tests/approved/Ran
                    ge-surroundContents.html
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
        AssignedTo: annevk@opera.com
        ReportedBy: stighal@opera.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, ayg@aryeh.name, www-dom@w3.org


Created attachment 1068
  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1068
Test patch

The surroundContents test [1] for Range expects an BAD_BOUNDARYPOINTS_ERR
exception in some cases, but the spec [2] now uses INVALID_STATE_ERR instead.

Patch attached.

[1]
http://w3c-test.org/webapps/DOMCore/tests/approved/Range-surroundContents.html
[2]
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-range-surroundcontents

-- 
Configure bugmail: https://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 Monday, 16 January 2012 12:12:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:09 GMT