XForms and Deprecating DOM* Events in DOM3 Events

Hi, XForms folks (& sundry interested parties)-

I previously mentioned to you that the DOMActivate, DOMFocusIn, and 
DOMFocusOut were being considered for deprecation in DOM3 Events.  After 
looking into the matter closely and talking with various invested 
parties, I've now deprecated them in current drafts of the spec [1]. 
I've explained some of the rationale for this in the HCG [2].

Note that this is deprecation, not removal... I took pains to fit them 
into the more precise coherent model we've worked out for DOM3 Events. 
Given XForms' use of DOMActivate in particular, I have put special 
provision to explain its place in the event flow for activation 
triggering and activation behavior [3].

Going forward, the XForms specs can continue to define DOMActivate [4], 
DOMFocusIn [5], and DOMFocusOut [6] as they already do, and 
implementations of XForms can maintain backwards compatibility with 
existing content.

Going forward, the XForms WG may wish to consider taking a fresh look at 
events as specified in DOM3 Events, which is rather more detailed than 
previous DOM events specs and tries to align more closely with actual 
implemented behavior, to see if aspects of it might be useful to XForms.

[1] http://dev.w3.org//2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
[2] 
http://lists.w3.org/Archives/Public/public-hypertext-cg/2010JanMar/0001.html
[3] 
http://dev.w3.org//2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-flow-activation
[4] http://www.w3.org/TR/xforms11/#evt-activate
[5] http://www.w3.org/TR/xforms11/#evt-DOMFocusIn
[6] http://www.w3.org/TR/xforms11/#evt-DOMFocusOut

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs

Received on Monday, 1 February 2010 08:41:25 UTC