RE: DOM Dependency

Dear all,

It seems to me that the ISSUE-10 describes the request from Anthony : This issue was raised at last summer F2F meeting in Santa Clara, and we said that it would be nice to make sure we are addressing any environment, browser based or not browser-based. Unfortunately, we did not have any proposal to formally review the spec, with that constraint. 

Personally I don’t remember non-browser framework were considered as out of scope during our discussion in Santa Clara and on the other hand, when the charter was designed, this case was not mentioned -which could explain why the webapp case is so popular in it.  We can argue hours about the charter interpretation but I think that we should start with a pragmatic approach to that. 

Is there any reasonable technical solution to cope with that constraint, that can be managed in a timeframe which fits with our deliverable roadmap ? Any proposal from the WG participants ?


-----Original Message-----
From: David Dahl [] 
Sent: mercredi 20 février 2013 07:50
To: Anthony Nadalin
Cc:; Alex Russell; Ryan Sleevi
Subject: Re: DOM Dependency

I am trying to imagine node.js mocking/implementing (properly) the EventTarget interface. That does not seem like it will work too well.

That being said, the WorkerCrypto interface might work better in a non-browser environment as a worker will not be as tied to the DOM.



----- Original Message -----
From: "Anthony Nadalin" <>
To: "Ryan Sleevi" <>
Cc:, "Alex Russell" <>
Sent: Tuesday, February 19, 2013 10:22:20 PM
Subject: RE: DOM Dependency

It has been discussed many times in this WG, the browser is not the only target for the APIs, stand-alone and server side are also targets, the specification should not have a dependency on DOM and a bug should be opened to resolve this.

-----Original Message-----
From: Ryan Sleevi []
Sent: Tuesday, February 19, 2013 2:30 PM
To: Anthony Nadalin
Cc:; Alex Russell
Subject: Re: DOM Dependency

On Tue, Feb 19, 2013 at 2:23 PM, Anthony Nadalin <> wrote:
> And also tasked for standalone environments so we should not have this 
> dependency as this is not a JS dependency

Can you point that out in the charter?

We're talking about the same dependency found in HTML - namely, the notion of a sane event model.

I'd be curious to see how you would propose an asynchronous API without events and without re-inventing events through some specification-specific dialect.

The phrase "Web Application" appears nine times in our charter, so surely this is not being seen as some new requirement. It's been this way since the start.

Received on Tuesday, 26 February 2013 18:18:08 UTC