On Fri, May 25, 2012 at 1:08 PM, Travis Leithead
<travis.leith...@microsoft.com> wrote:
>> -----Original Message-----
>> From: Travis Leithead
>> Sent: Thursday, March 8, 2012 3:31 PM
>>
>> Hey folks,
>>
>> I'm joining Jacob Rossi to help work on editing the DOM L3 Events spec; I 
>> have
>> some time to address some of the editorial last call comments, and I hope to
>> move through them all pretty quickly.
>>
>> I know there are a variety of opinions out there regarding the DOM L3 Events
>> spec, and what should be done with it. I'm going to start with the basis 
>> that it's a
>> good spec. It provides a great deal of context into the event dispatch model 
>> (in
>> the form of prose, versus the new algorithmic approach that has been popular
>> since the HTML5 spec first hit the scene). It also describes basic concepts 
>> such as
>> default actions and their effect on cancelable events, trusted events, etc., 
>> for
>> which having a central reference is quite informative. In addition to the 
>> common
>> event types, it also defines the elusive KeyboardEvent, a hallmark of this 
>> spec
>> since the beginning.
>>
>> This spec is certainly aging. It's one of the oldest specs that is still in 
>> active
>> development. I can see working drafts of DOM Level 3 events dating back to
>> September 1st, 2000 [1]. Many, many folks have contributed to, reviewed, and
>> provided feedback on this spec along the way. With the relatively youthful
>> DOM4 spec poised to take the torch for the next round of DOM event
>> functionality, I'd prefer to close up any lingering issues with DOM L3 
>> Events, get
>> it done (to Recommendation status), and turn my attention to DOM4. Getting
>> DOM L3 Events to Rec is a very important milestone for UAs and
>> implementations like IE, that have made a commitment to supporting this spec,
>> have an existing implementation, and need a stable reference specification 
>> for
>> our customers and partners.
>>
>> To support the goal of finishing DOM Level 3 Events (in light of the current 
>> work
>> happening in DOM4), I'm jumping in to help Jacob finish addressing last call
>> comments. I've interested in ensuring that the concepts and normative
>> requirements of DOM Level 3 Events do not conflict with the existing model
>> described in DOM4. In this way, I think DOM4 will be a natural succession 
>> from
>> DOM Level 3 Events and will add to the richness of the eventing platform on 
>> the
>> web.
>>
>> I've already made a few changes to the spec in regard to some existing last 
>> call
>> comments [2]. I'm not done. I'll be officially working through bugs filed in 
>> the
>> "DOM3 Events" component of the W3C Bug Tracker [3], and will be moving
>> other issues from Tracker [4] into that system to make my life easier. 
>> Please file
>> new comments as bugs, and I'll follow up there.
>
> Quick follow-up:
> To my knowledge all remaining Tracker issues and other feedback previously 
> sent to Jacob have now been resolved in the Bugzilla component for DOM3 
> Events save one last issue. I'm currently working through the final issue 
> (accessibility feedback) but didn't want to wait until that was resolved 
> before sending this mail. The spec has been dramatically updated in the past 
> 3 months, and should now be quite nicely aligned with DOM4's Events section.
>
> My plan, as mentioned at the March F2F meeting, is to resolve the last issue, 
> then ask the chairs to start the LC process for this spec, with advancement 
> to CR hopefully following soon thereafter.
>
> This is not yet an official last call, but if you'd like to re-read the spec 
> and provide additional feedback--this is a good time to do it. Also, if for 
> some reason I missed responding to your previously written feedback, please 
> re-send it or file a bug directly.
>
> DOM3 Events (Ed. Draft) 
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
> DOM4 Events section (WD) http://www.w3.org/TR/dom/#events

Yay! Awesome! Thanks for slugging through this work. Looking forward to LC soon!

/ Jonas

Reply via email to