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 641 - DOMErrorMonitor not connected in L3 Core tests
Summary: DOMErrorMonitor not connected in L3 Core tests
Status: RESOLVED FIXED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 3 (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Curt Arnold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-30 00:34 UTC by Curt Arnold
Modified: 2004-03-30 05:43 UTC (History)
0 users

See Also:

Attachments
Hook up error handler, plus other small fixes (37.91 KB, patch)
2004-03-30 00:39 UTC, Curt Arnold 		Details

Description Curt Arnold 2004-03-30 00:34:51 UTC 
Many L3 Core tests constructed a DOMErrorMonitor and checked that no errors 
were raised but never connected the monitor using setParameter("error-handler")
Comment 1 Curt Arnold 2004-03-30 00:39:59 UTC 
Created attachment 332 [details]
Hook up error handler, plus other small fixes

Add canonicalform12 which checks that doctype is dropped.
Removed duplicate test datatypenormalization19
Fixed datatypenormalization17 and 18 due to trailing blanks having been
stripped from datatype.
Eliminated erroneous check of doctype in datatypenormalization01 (it should
have been dropped)