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 15583 - BAD_BOUNDARYPOINTS_ERR no longer used for Range
Summary: BAD_BOUNDARYPOINTS_ERR no longer used for Range
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Stig Halvorsen
QA Contact: public-webapps-bugzilla
URL: http://w3c-test.org/webapps/DOMCore/t...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-16 12:12 UTC by Stig Halvorsen
Modified: 2012-01-16 14:20 UTC (History)
4 users (show)

See Also:

Attachments
Test patch (1.22 KB, patch)
2012-01-16 12:12 UTC, Stig Halvorsen 		Details

Description Stig Halvorsen 2012-01-16 12:12:03 UTC 
Created attachment 1068 [details]
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
Comment 1 Ms2ger 2012-01-16 14:20:10 UTC 
http://dvcs.w3.org/hg/webapps/rev/c3f0efcefb07

Thanks!