This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#script-processing-for Comment: "event" and "for" attributes are obsolete Posted from: 188.46.158.206
The "event" and "for" attributes of the <script> element have been unconditionally obsoleted and should be deleted from the abovementioned paragraph.
The spec text you cite relates to processing requirements, not document-conformance requirements. The approach around requirements of this kind that is used is the spec is basically to specify what authors must not do, but then to also specify what processing applications -- UAs/browsers -- must do even for cases where authors/documents don't follow the rules. There are a number of other instances in the spec where processing requirements are given for handling of invalid attributes. The rationale for that is that that are existing documents that use the attributes, so we need to try to define processing requirements for them so that we can have some chance of getting interoperable behavior among various browsers with respect to them. If you have some information about why the circumstances for handling of these attributes is somehow different from that for other attributes that are invalid but that have defined processing requirements, please post it here.
Thanks, Michael, I now see the difference. But I suggest to tag these elements in the document description as obsoleted, so that it becomes clear. Like: "If the script element has an event[*] attribute and a for[*] attribute"