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 14589 - assert_throws() needs to handle new DOMException types and stop handling RangeException
Summary: assert_throws() needs to handle new DOMException types and stop handling Rang...
Status: RESOLVED FIXED
Alias: None
Product: Testing
Classification: Unclassified
Component: testharness.js (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: James Graham
QA Contact: James Graham
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14590
  Show dependency treegraph
 
Reported: 2011-10-28 18:48 UTC by Aryeh Gregor
Modified: 2011-11-15 19:21 UTC (History)
1 user (show)

See Also:


Attachments
Patch (4.25 KB, patch)
2011-10-28 18:48 UTC, Aryeh Gregor
Details

Description Aryeh Gregor 2011-10-28 18:48:39 UTC
Created attachment 1038 [details]
Patch

DOM4 has added a couple of new exception types, and RangeException has been removed.  The upshot is that assert_throws() is now incorrect for INVALID_NODE_TYPE_ERR if the UA implements RangeException but doesn't yet implement INVALID_NODE_TYPE_ERR in DOMException.  Firefox 9.0a2 spuriously passes tests that require INVALID_NODE_TYPE_ERR because it hasn't added that type to DOMException yet, while Chrome 16 dev fails them because it has.  Firefox should fail too, and the assert should work the same regardless of what types the UA supports in DOMException.
Comment 1 Aryeh Gregor 2011-11-15 19:21:31 UTC
http://dvcs.w3.org/hg/html/rev/dd38526bcd57