ACTION-180: Provide a text update to section 4.3 to resolve issue 116 and ISSUE-84
Provide a text update to section 4.3 to resolve issue 116 and ISSUE-84
- State:
- pending review
- Person:
- Nick Doty
- Due on:
- May 23, 2012
- Created on:
- April 12, 2012
- Associated Issue:
- ISSUE-116
- Related emails:
- Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from cblouch@aol.com on 2012-07-20)
- Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from jmayer@stanford.edu on 2012-07-18)
- Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from ed@felten.com on 2012-07-18)
- Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from npdoty@w3.org on 2012-07-17)
- Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from singer@apple.com on 2012-05-30)
- ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from npdoty@w3.org on 2012-05-30)
- agenda: 30 May 2012 call (from aleecia@aleecia.com on 2012-05-29)
Related notes:
There are concerns that the proposal in Section 4.3 does not work (ISSUE-116 and ISSUE-84). Could you propose a text update to fix this?
Matthias Schunter, 12 Apr 2012, 23:40:26Handing from Tom to Nick; adding a week
Aleecia McDonald, 9 May 2012, 16:21:27Display change log.