Re: [whatwg] Counterproposal for canvas in workers

2013-10-20 Thread Kyle Huey
I think most of these have been said already, but my issues with (my understand of?) this proposal are: 1. It requires defining a new script execution environment different from both the main thread and workers. That seems like a lot of unnecessary work. And this execution environment is either

Re: [whatwg] Synchronizing Canvas updates in a worker to DOM changes in the UI thread

2013-10-20 Thread Kyle Huey
On Sun, Oct 20, 2013 at 11:33 PM, Glenn Maynard gl...@bluegoji.com wrote: It must not be possible for the UI thread to detect whether present() did anything--if there's no frame in the ready buffer, nothing changes and the UI thread can't detect this. Similarly, it must not be possible for

[whatwg] Canvas in workers

2013-10-12 Thread Kyle Huey
I talked at length with Robert O'Callahan about what the DOM API for supporting canvas in web workers should look like and we came up with the following modifications to the spec. 1. Rename CanvasProxy to WorkerCanvas and only allow it to be transferred to workers. I don't think we're

Re: [whatwg] Canvas in workers

2013-10-12 Thread Kyle Huey
the editor's draft of canvas 2d context and I have some familiarity with DOM. But I do not understand what you are referencing to worker, missing some lingo here. Can you expand on that? Cheers, Mike Sent by the hope boat. On Oct 13, 2013, at 12:12 AM, Kyle Huey m...@kylehuey.com wrote: I

Re: [whatwg] Canvas in workers

2013-10-12 Thread Kyle Huey
On Sun, Oct 13, 2013 at 12:50 PM, Michael Norton no...@me.com wrote: Thank you! Read over the 1st link you provided, interesting. A worker then seems similar to a runtime process in an os environment - is it a derivation of RPC? In a manner of speaking. Workers are an abstraction

[whatwg] [Workers] CSP and SharedWorkers

2013-09-25 Thread Kyle Huey
It's unclear how SharedWorkers should interact with Content Security Policies. This came up during code review of the SharedWorker implementation in Gecko[0]. There was a public-webappsec thread[1] on this back in May that didn't really reach a conclusion and I'd like to drive towards one here.

Re: [whatwg] Detecting eventListeners

2012-05-24 Thread Kyle Huey
On Thu, May 24, 2012 at 6:34 PM, Xavier Ho cont...@xavierho.com wrote: Hello, We're working on a project that requires detection of registered event listeners. I'll bite. Why do you care if an EventTarget has registered event listeners or not? - Kyle

Re: [whatwg] Detecting eventListeners

2012-05-24 Thread Kyle Huey
On Thu, May 24, 2012 at 8:27 PM, Glenn Maynard gl...@zewt.org wrote: Making event listeners enumerable would remove that property. As I read it, he is not asking to enumerate event listeners. Simply to know if there are any for the event in question. Something like partial interface

Re: [whatwg] Video- and audio-controls without scripting

2011-08-14 Thread Kyle Huey
On Sun, Aug 14, 2011 at 3:33 AM, Timo Beermann timo.beerm...@googlemail.com wrote: The new video- and audio-tag are great, but the controls (play/pause, skip forward, skip back, volume, progress bar, time) should be possible without scripting. Some standard-controls that also can be modified

Re: [whatwg] Proposing canvas.toBlob(contentType)

2011-04-14 Thread Kyle Huey
. dave On Wed, Apr 13, 2011 at 3:02 PM, Kyle Huey m...@kylehuey.com wrote: Hello All, Gecko 2.0 ships with a non-standard method on canvas named mozGetAsFile(contentType, fileName). We added this for internal use in our UI. It retrieves the contents of the canvas as a File object

[whatwg] Proposing canvas.toBlob(contentType)

2011-04-13 Thread Kyle Huey
Hello All, Gecko 2.0 ships with a non-standard method on canvas named mozGetAsFile(contentType, fileName). We added this for internal use in our UI. It retrieves the contents of the canvas as a File object (at the time Gecko did not supports Blobs) encoded in the contentType according to the

Re: [whatwg] [WHATWG] HTMLElement ids as global object properties

2011-04-01 Thread Kyle Huey
This is often called global scope pollution and is defined in the spec at http://www.whatwg.org/specs/web-apps/current-work/#dom-window-nameditem. I believe that in Firefox 4 you should only be seeing this behavior in quirks mode. There is a bug on file at