W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2011

Conflicts between D3E and Web DOM Core

From: Jacob Rossi <jrossi@microsoft.com>
Date: Thu, 3 Mar 2011 22:06:33 +0000
To: "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <D0BC8E77E79D9846B61A2432D1BA4EAE0275DFC1@TK5EX14MBXC110.redmond.corp.microsoft.com>
I've identified some potential conflicts between Web DOM Core and DOM L3 Events:

 1. WDC allows the dispatch of an event without having initialized its event object (e=document.creatEvent("Event"); window.dispatchEvent(e);). No major browser supports this today and there are not any valid use cases for this behavior (that I can think of), so why make implementations change?

2. cancels and bubbles are now optional arguments for initEvent() in WDC.  How does this merge with the other init___Event( ) methods which are have cancels and bubbles in the middle of their methods? I think there's some support for improving how the init methods behave, but this doesn't really solve that problem. I'd rather see D3E keep these are required and then Web DOM Core consider taking the task of event object constructors. [1]

3. Event names can be empty strings but not null in WDC [2]. Why exclude null, it's not any more nonsensical than "". IE9, Chrome, and Opera all allow null as a name.

4. Calls to dispatchEvent(evt) where evt is an event object that's already in the middle of dispatch throw an INVALID_STATE_ERR according to WDC [3], but a DISPATCH_REQUEST_ERR according to D3E [4]. Why change the name/code?



[1] http://www.w3.org/2008/webapps/track/issues/129 
[2] http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-eventtarget-addeventlistener
[3] http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-eventtarget-dispatchevent
[4] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-EventException 
From: Arthur Barstow <art.barstow@nokia.com>
Date: Thu, 03 Mar 2011 06:54:08 -0500
Message-ID: <4D6F8160.2090301@nokia.com>
To: public-webapps <public-webapps@w3.org>
Hi All,

There is significant support for this CfC and in general, I tend to 
favor PEPO (publish early, publish often).

However, in this case, the group already agreed D3E is feature complete 
and it would be suboptimal (some have suggested harmful), for WebApps to 
publish a spec that conflicts/overlaps with D3E. Additionally, some 
members have been working on D3E for a relatively long time and they 
naturally want to preserve their investment.

Doug expressed [DS] willingness to change D3E (to align with DOM Core 
Events) if there is broad consensus for changes. In this spirit of 
cooperation, before a new WD of DOM Core is published, I think the next 
step is to do as Doug suggested and identify all D3E issues.

Anne asked [AvK] about the mechanism to use to identify issues. Unless 
Doug suggests otherwise, I recommend using a separate thread per issue 
on the www-dom mail list.

-Art Barstow

[DS] http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0687.html

On Feb/23/2011 11:20 AM, ext Arthur Barstow wrote:
> Anne and Ms2ger (representing Mozilla Foundation) have continued to 
> work on the DOM Core spec and they propose publishing a new Working 
> Draft of the spec:
> http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html
> As such, this is a Call for Consensus (CfC) to publish a new WD of DOM 
> Core. If you have any comments or concerns about this proposal, please 
> send them to public-webapps by March 2 at the latest.
> As with all of our CfCs, positive response is preferred and encouraged 
> and silence will be assumed to be agreement with the proposal.
> -Art Barstow
Received on Thursday, 3 March 2011 22:07:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:17 UTC