W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2011

[Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers

From: <bugzilla@jessica.w3.org>
Date: Fri, 04 Mar 2011 02:06:50 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PvKPq-0004Bn-0p@jessica.w3.org>

--- Comment #4 from Allen Wirfs-Brock <allen@wirfs-brock.com> 2011-03-04 02:06:49 UTC ---
(In reply to comment #2)
> Based on my reading the spec, it looks like we actually need to do a little
> more than was proposed in comment 0, so please do check to make sure I didn't
> screw anything up.

Step 4 should (its also wrong in ES5 be:
<p>If <var title="">body</var> is not parsable as <i>FunctionBody</i> or if
parsing detects an early error then abort these steps.</p>

<p class="note"><i>FunctionBody</i> is defined in ECMAScript edition 5 section
13 Function Definition. "Early error" is defined in ECMAScript edition 5
section 16 Errors.<a href="#refsECMA262">[ECMA262]</a></p>

Step 6 is unnecessary, as the specific strict mode restrictions in ES5 section
13.1 relate to the naming of the formal parameters of a function and the fixed
set of names you provide in step 7 don't violate any of those restrictions.

> It would be really nice if the JS spec could just give us hooks that we could
> use so that we didn't have to worry about updating HTML every time the JS spec
> revs.

I agree with the goal, but there are some missing ES semantics we still need to
address. In this particular case, I think we may be able to describe the
desired semantics as a source-to-source transformation of the ES code and avoid
having to explicitly reach into the ES5 internal spec. mechanisms.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 4 March 2011 02:06:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:44 UTC