ACTION-1753: Propose making DOMActivate optional in the light that there needs to be a single definition point for a definition already in place for ten yewards, to point out that HTML5 is not the only consumer of DOM Events, and that there are already DOMActivate implementations in DOM Level 2 implementations which would likely provide CR exit for the DOM 3, and that the Apple User Interface Independence proposal at http://lists.w3.org/Archives/Public/www-dom/2010JulSep/att-0106/UserInterfaceIndependence.html strengthens the future case for abstract events.: http://lists.w3.org/Archives/Public/public-forms/2010Oct/att-0027/2010-10-27.html#ACTION2
Propose making DOMActivate optional in the light that there needs to be a single definition point for a definition already in place for ten yewards, to point out that HTML5 is not the only consumer of DOM Events, and that there are already DOMActivate implementations in DOM Level 2 implementations which would likely provide CR exit for the DOM 3, and that the Apple User Interface Independence proposal at http://lists.w3.org/Archives/Public/www-dom/2010JulSep/att-0106/UserInterfaceIndependence.html strengthens the future case for abstract events.: http://lists.w3.org/Archives/Public/public-forms/2010Oct/att-0027/2010-10-27.html#ACTION2
- State:
- open
- Person:
- Steven Pemberton
- Due on:
- November 27, 2010
- Created on:
- October 27, 2010
- Associated Product:
- All
- Related emails:
- No related emails
Related notes:
No additional notes.
Display change log.