This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
No browser can pass both level1/html/HTMLBaseFontElement03.html and level2/html/HTMLBaseFontElement03.html The first one tests that size returns a number, the second one tests that size returns a string. Can the level1 test be removed, since the test is obsoleted by the one on level2? Another approach would to enable that test only if !hasFeature("HTML","2.0")...
Same thing for all the attributes whose types have been changed. HTMLInputElement13.html HTMLImageElement05.html HTMLImageElement06.html HTMLImageElement11.html HTMLImageElement12.html HTMLImageElement14.html HTMLObjectElement01.html HTMLObjectElement11.html HTMLObjectElement16.html I fail to see any purpose in requiring that new browsers implement the outdated version of the specs :)
to curt.
Created attachment 289 [details] Skips affected tests if hasFeature("HTML", "2.0") is true
I've guarded the tests in the L1 suite that are affected by type changes in L2 so the body of the test will be skipped if hasFeature("HTML", "2.0") returns true. The L2 HTML test suite incorporates all appropriate L1 HTML tests, so there should be a vanishingly small need for the L1 HTML test suite.
Created attachment 293 [details] Defining doc as 'Document' avoids weakness in test-to-java