Revision Summary Date Revision History Revision Class Comments 4/17/2015 1.0 New Released new document 7/7/2015 1.1 Minor Clarified the meaning of the technical content. 11/2/2015 1.2 Minor Clarified the meaning of the technical content. 3/22/2016 1.3 Minor Clarified the meaning of the technical content. 7/19/2016 1.4 Clarified the meaning of the technical content. 11/2/2016 1.4 None No changes to the meaning, language, or formatting of the technical content. 3/14/2017 1.4 None No changes to the meaning, language, or formatting of the technical content. 10/3/2017 1.4 None No changes to the meaning, language, or formatting of the
technical content. 1/23/2018 1.4 None No changes to the meaning, language, or formatting of the technical content. 2/22/2018 1.4 None No changes to the meaning, language, or formatting of the technical content. 3/23/2018 1.4 None No changes to the meaning, language, or formatting of the technical content. 8/28/2018 1.5 Minor Clarified the meaning of the technical content.
4.2.6 The element ... The disabled IDL attribute behaves as defined for the alternative style sheets DOM. IE11 Mode, IE10 Mode, IE9 Mode, IE8 Mode, IE7 Mode, and IE5 (Quirks) Mode (All versions) The disabled attribute is not supported. V0032: No error event is fired on the style element in the case of a Content-Type mismatch The specification states: 4.2.6 The style element ... Once the attempts to obtain the style sheet's critical subresources, if any, are complete, or, if the style sheet has no critical subresources, once the style sheet has been parsed and processed, the user agent must, if the loads were successful or there were none, queue a task to fire a simple event named load at the style element, or, if one of the sheet's critical subresources failed to completely load for any reason (e.g. DNS error, HTTP 404 response, a connection being prematurely closed, unsupported Content-Type), queue a task to fire a simple event named error at the element. ... All document modes (All versions) No event is fired on the style element in the case of a Content-Type mismatch. [HTML5] Section 4.3.1 The body element The onerror event handler does not replace the generic event handler The specification states: 4.3.1 The body element ... The onblur, onerror, onfocus, onload, onresize, and onscroll event handlers of the Window object, exposed on the body element, replace the generic event handlers with the same names normally supported by HTML elements. All document modes (All versions) The onerror event handler does not replace the generic event handler. The onpagehide and onpageshow event handlers are not supported The specification states: 4.3.1 The body element ... Content attributes: ... onpagehide
[HTML5] Section 4.10.22.6 URL-encoded form data V0205: URL-encoded form data is encoded in UTF-8 regardless of what is in accept-charset The specification states: ... URL-encoded form data ... The application/x-www-form-urlencoded encoding algorithm is as follows: All document modes (All versions) URL-encoded form data is encoded in UTF-8 regardless of what is in accept-charset. V0206: URL-encoded form data includes the full filepath for type file, not the file name alone The specification states: ... URL-encoded form data ... The application/x-www-form-urlencoded encoding algorithm is as follows: All document modes (All versions) URL-encoded form data includes the full file path for type file, not the file name alone. [HTML5] Section 4.10.22.7 Multipart form data Forms are always encoded as UTF-8 The specification states: ... Multipart form data The multipart/form-data encoding algorithm is as follows: ... 2. If the algorithm was invoked with an explicit character encoding, let the selected character encoding be that encoding. ... ... Otherwise, let the selected character encoding be UTF-8. All document modes (All versions) are always encoded as UTF-8. [HTML5] Section 4.10.22.8 Plain text form data V0208: The submitted data set includes the full path of the file, not just the filename The specification states:
V0228: The :invalid pseudo-class does not match a fieldset element if that element has a child that is an :invalid candidate element The specification states: ... Pseudo-classes ... :invalid The :invalid must match any element falling into one of the following categories: .. • fieldset elements that have of one or more descendant elements that themselves are candidates for constraint validation but do not satisfy their constraints All document modes (All versions) The :invalid pseudo-class does not match a fieldset element if that element has a child that is an :invalid candidate element. V0224: The :default state is not supported The specification states: 4.14.2 Pseudo-classes ... :default The :default pseudo-class must match any element falling into one of the following categories: IE11 Mode, IE10 Mode, IE9 Mode, IE8 Mode, IE7 Mode, and IE5 (Quirks) Mode (All versions) The :default state is not supported. The :link pseudo-class does not match area or link elements with href attributes The specification states: ... Pseudo-classes ... :link :visited All a elements that have an href attribute, all area elements that have an href attribute, and all link elements that have an href attribute, must match one of :link and :visited. All document modes (All versions) The :link pseudo-class does not match area or link elements with href attributes.