This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Actual results -------------- line 23 * <script src="/resources/testharness.js"></script> line 24 * <script src="/resources/testharnessreport.js"></script> Expected results ---------------- line 23 * <script type="text/javascript" src="/resources/testharness.js"></script> line 24 * <script type="text/javascript" src="/resources/testharnessreport.js"></script> Gérard
Per HTML5 [1], the default value of the type attribute is text/javascript, so there is no need to specify it... [1] http://www.w3.org/TR/html5/the-script-element.html#the-script-element
> Per HTML5 [1], the default value of the type attribute is text/javascript, > so there is no need to specify it... > > [1] http://www.w3.org/TR/html5/the-script-element.html#the-script-element The usage of testharness.js is not restricted to HTML5 (which isn't even finalized PR yet). In fact, the http://w3c-test.org/resources/testharness.js is intended for XHTML 1 documents. I created this bug report because many script-based tests at http://test.csswg.org/suites/ were having validation errors in part simply due to the missing of that attribute. In general, it's best to avoid issues when creating an how-to-use document for multiple use. If testharness.js is used for HTML4 or HTML5 or XHTML1 documents, then what's the most flexible and valid way to declare scripts? Gérard