W3C home > Mailing lists > Public > public-webcrypto@w3.org > February 2013

Re: DOM Dependency

From: Nadim Kobeissi <nadim@nadim.cc>
Date: Tue, 19 Feb 2013 17:31:07 -0500
Message-ID: <CAOZ60qARCkTDtnUXp3d=TUjPagWW42NDDSBy8U3Z8+X+kgLkMw@mail.gmail.com>
To: Ryan Sleevi <sleevi@google.com>
Cc: Anthony Nadalin <tonynad@microsoft.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Alex Russell <slightlyoff@google.com>
That's cool. Because right now window.getRandomValues() doesn't work within
web workers and that's a pain for Cryptocat — we have to work around it.


NK


On Tue, Feb 19, 2013 at 5:27 PM, Ryan Sleevi <sleevi@google.com> wrote:

> No.
>
> While access to the DOM is prohibited, the notion of Events (as
> explored in HTML) also derives from a normative reference on the
> DOMEVENTS specification, and is core to the Web Workers specification
> itself (namely, the onmessage event)
>
>
>
> On Tue, Feb 19, 2013 at 2:21 PM, Nadim Kobeissi <nadim@nadim.cc> wrote:
> > Does this dependency affect the API's capability of working within a web
> > worker?
> >
> >
> > NK
> >
> >
> > On Tue, Feb 19, 2013 at 5:19 PM, Ryan Sleevi <sleevi@google.com> wrote:
> >>
> >> On Tue, Feb 19, 2013 at 2:10 PM, Anthony Nadalin <tonynad@microsoft.com
> >
> >> wrote:
> >> > Why is there a DOM dependency in the API specification?
> >> >
> >> >
> >>
> >> Because this is the _Web_ Crypto API, tasked with delivering an API
> >> suitable for conforming user agents.
> >>
> >> Among the many concepts we borrow are the notion of Events, Event
> >> Targets, dispatching events, and the lifetime model that is inherently
> >> linked to the DOM and HTML specifications.
> >>
> >> This dependency is reflected in Section 4.1 of our charter.
> >>
> >
>
Received on Tuesday, 19 February 2013 22:31:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 February 2013 22:31:55 GMT