On 2013/10/19 3:19, Justin Novosad wrote:
Please share your thoughts.
I think it these events are needed, unfortunately, as it doesn't look
like GPU contexts will be virtualized any time soon.
For the open issues, I say yes to the first. Note that this matches what
is said about the
On Tue, Oct 22, 2013 at 12:39 AM, Glenn Maynard gl...@zewt.org wrote:
Using ImageBitmap for this has a lot of issues. It requires synchronizing
with scripts in the UI thread. It requires manualling resize your canvas
repeatedly to fit different destinations. It also may potentially create
On Fri, Oct 18, 2013 at 10:56 PM, Boris Zbarsky bzbar...@mit.edu wrote:
So it looks to me like in practice Element.getElementById could be quite a
bit faster than the equivalent querySelector call, for both the in-tree case
(where both can avoid walking the tree) and the out-of-tree case (where
On Tue, Oct 22, 2013 at 3:07 AM, Mark Callow callow.m...@artspark.co.jpwrote:
I say a weak no to the second. Testing can be done with shims and there
are probably better ways for apps to do resource management.
After doing some digging, I totally agree. I found that the webgl debug
utilities
I just noticed that Canvas already has a Canvas.setContext() method, which
seems to do exactly what I'm proposing, even down to clearing the
backbuffer on attach. The only difference is that it lives on Canvas
instead of the context--the only reason I put it there in my proposal was
because this
On Oct 21, 2013 6:06 PM, Ehsan Akhgari eh...@mozilla.com wrote:
We could further define that channeldropped is fired when the owner
of the *other side* is navigated away from. This would mean that
events can be received even after a channeldropped event has been
fired since other windows could
On Oct 21, 2013 6:08 PM, Ehsan Akhgari eh...@mozilla.com wrote:
How does this work - imagine that I have a reference to a MessagePort,
but I'm not actively waiting for any response on the port so I don't have a
channeldropped event listener.
Now, the remote side of the port crashes. I send a
On Tue, Oct 22, 2013 at 11:36 AM, Jonas Sicking jo...@sicking.cc wrote:
On Oct 21, 2013 6:08 PM, Ehsan Akhgari eh...@mozilla.com wrote:
How does this work - imagine that I have a reference to a MessagePort,
but I'm not actively waiting for any response on the port so I don't have a
On Tue, Oct 22, 2013 at 4:37 PM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Oct 22, 2013 at 2:48 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
This code actually does something potentially useful which can't easily
be
done with attachToCanvas: generating a series of images as fast as
On Tue, Oct 22, 2013 at 7:37 AM, Glenn Maynard gl...@zewt.org wrote:
I just noticed that Canvas already has a Canvas.setContext() method
That's there in support of CanvasProxy, which is a flawed API and
which this entire discussion is aiming to rectify.
, which
seems to do exactly what I'm
On Mon, Oct 21, 2013 at 8:03 AM, Glenn Maynard gl...@zewt.org wrote:
On Sun, Oct 20, 2013 at 11:53 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
Glenn, taking a step back for a bit, is there anything in
https://wiki.mozilla.org/User:Roc/WorkerCanvasProposal that you would
actually object
On Tue, Oct 22, 2013 at 9:31 AM, Ehsan Akhgari eh...@mozilla.com wrote:
interface MessagePort {
...
Promise pin();
void unpin(optional any value);
};
Rather than firing channeldropped we reject any promise returned from
pin(). Once the caller receives an expected answer he/she calls
On Tue, Oct 22, 2013 at 1:32 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Oct 22, 2013 at 9:31 AM, Ehsan Akhgari eh...@mozilla.com wrote:
interface MessagePort {
...
Promise pin();
void unpin(optional any value);
};
Rather than firing channeldropped we reject any promise
On Oct 22, 2013, at 4:00 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Oct 18, 2013 at 10:56 PM, Boris Zbarsky bzbar...@mit.edu wrote:
So it looks to me like in practice Element.getElementById could be quite a
bit faster than the equivalent querySelector call, for both the in-tree
On Tue, Oct 22, 2013 at 7:42 PM, Ryosuke Niwa rn...@apple.com wrote:
On Oct 22, 2013, at 4:00 AM, Anne van Kesteren ann...@annevk.nl wrote:
So do you think we should add getElementById() to ParentNode in DOM?
Why not to Element?
ParentNode encompasses Document, DocumentFragment, and Element.
On Tue, Oct 22, 2013 at 7:31 PM, Kenneth Russell k...@google.com wrote:
Robert, please don't remove those APIs from your proposal. They're
needed in order to address known use cases, and splitting them off
will make it difficult to understand how they interact with
WorkerCanvas later.
Yes,
On Tue, Oct 22, 2013 at 1:44 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Tue, Oct 22, 2013 at 7:31 PM, Kenneth Russell k...@google.com wrote:
Robert, please don't remove those APIs from your proposal. They're
needed in order to address known use cases, and splitting them off
will
I got an account and I'm uploading the proposal now.
Rob
--
Jtehsauts tshaei dS,o n Wohfy Mdaon yhoaus eanuttehrotraiitny eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.rt sS?o Whhei csha iids teoa
stiheer :p atroa lsyazye,d 'mYaonu,r sGients uapr,e tfaokreg iyvoeunr,
'm aotr
Great.
On Tue, Oct 22, 2013 at 2:54 PM, Robert O'Callahan rob...@ocallahan.org wrote:
I got an account and I'm uploading the proposal now.
Rob
--
Jtehsauts tshaei dS,o n Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le
atrhtohu gthot sf oirng iyvoeu rs ihnesa.rt sS?o Whhei csha iids
On Tue, Oct 22, 2013 at 10:44 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
No problem at all. Can you do it? I need to get a WHATWG account :-).
OK, I added the proposal here:
http://wiki.whatwg.org/wiki/WorkerCanvas
A couple of changes from the previous version:
-- Added
On Tue, Oct 22, 2013 at 2:48 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
This code actually does something potentially useful which can't easily
be
done with attachToCanvas: generating a series of images as fast as
possible
which will be processed on another thread in some way
On 10/15/13 1:00 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 26 Jan 2013, Steve Faulkner wrote:
Lists are appropriate for indicating nested tree structures. The use of
lists to markup comments is a common mark up pattern used in blogging
software such as wordpress. The code verbosity is
On 10/22/13 2:42 PM, Ryosuke Niwa wrote:
Because of HTMLCollection's name getter, all major browsers must be capable of
a id+name lookup at every element (since Element has getElementsByTagName that
returns a HTMLCollection).
While true, in practice pretty much no one uses the name getter on
On 10/22/13 7:00 AM, Anne van Kesteren wrote:
So do you think we should add getElementById() to ParentNode in DOM?
I actually do, yes.
It seems the advantages are that we can optimize it better than
querySelector() because there is no selector parsing.
This, in my mind, is a somewhat minor
24 matches
Mail list logo
