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 Wednesday, 20 February 2013 06:50:25 UTC