On Fri, Jan 8, 2016 at 11:08 AM, Jeff Gilbert wrote:
> On Wed, Jan 6, 2016 at 8:07 PM, Luke Wagner wrote:
> > FWIW, I was wondering if we could go a step further and allow
> > (optional) user interaction with the rendered DOM elements. That way
> >
On Thu, Jan 7, 2016 at 8:46 PM, Anne van Kesteren wrote:
> At least enforcing CORS-same-origin would be somewhat trivial from a
> specification perspective since all fetches go through Fetch. Limiting
> plugins and other affected features would be some added conditionals
> here
On Thursday 2016-01-07 08:52 +0100, Anne van Kesteren wrote:
> On Thu, Jan 7, 2016 at 6:05 AM, L. David Baron wrote:
> > This specification is derived from an upstream WHATWG specification.
>
> And therefore hasn't removed the storage mutex concept it seems. Not
> sure if
On Fri, Jan 8, 2016 at 2:36 PM, Jeff Gilbert wrote:
> I think rather we should aim to provide a way for the application to
> implement custom remapping of events. A simple version of this is
> allowing the app to synthesize enough of the inputs to virtually use
> our
I think rather we should aim to provide a way for the application to
implement custom remapping of events. A simple version of this is
allowing the app to synthesize enough of the inputs to virtually use
our existing UI. I think this is much simpler than dredging around in
the WebGL API.
On Thu,
Kyle Huey writes:
> In Bug 1059469 I added a logging module for calls to dump() on Window
> and WorkerGlobalScope. You can enable it with
> NSPR_LOG_MODULES="Dump:5". This is really handy when you're using
> other logging modules and want to see how content script execution
On Thu, Jan 7, 2016 at 4:27 AM, Anne van Kesteren wrote:
> On Thu, Jan 7, 2016 at 10:24 AM, L. David Baron wrote:
> > Could you give a brief explanation of what the storage mutex is, and
> > why it was/should be removed?
>
> It prevents races for storage and
On Fri, Jan 8, 2016 at 9:58 AM, wrote:
> There are two use cases for this functionality needed by the WebVR team.
>
> The one needed earliest is to implement HUD interfaces and dialogues. In
> this case, we will only be using this API from chrome privileged code.
>
On Wed, Jan 6, 2016 at 8:07 PM, Luke Wagner wrote:
> FWIW, I was wondering if we could go a step further and allow
> (optional) user interaction with the rendered DOM elements. That way
> you could, say, select text on a 3d surface with a mouse or use an
> tag. It seems
On Thursday, January 7, 2016 at 1:32:59 AM UTC-8, Robert O'Callahan wrote:
> On Thu, Jan 7, 2016 at 8:46 PM, Anne van Kesteren wrote:
>
> > At least enforcing CORS-same-origin would be somewhat trivial from a
> > specification perspective since all fetches go through Fetch.
In Bug 1059469 I added a logging module for calls to dump() on Window
and WorkerGlobalScope. You can enable it with
NSPR_LOG_MODULES="Dump:5". This is really handy when you're using
other logging modules and want to see how content script execution
fits into the logging output.
- Kyle
11 matches
Mail list logo