W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: exposing CANVAS or something like it to Web Workers

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 14 May 2012 19:32:46 -0700
Message-ID: <4FB1C04E.7060900@jumis.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "Gregg Tavares (勤)" <gman@google.com>, public-webapps@w3.org
On 5/14/2012 7:24 PM, Boris Zbarsky wrote:
> On 5/14/12 10:18 PM, Charles Pritchard wrote:
>> On 5/14/2012 7:09 PM, Boris Zbarsky wrote:
>>> On 5/14/12 10:00 PM, Charles Pritchard wrote:
>>>> What would web fonts do in this situation, in Mozilla?
>>> Probably cry. ;)
>>>> If I've confirmed that a font is loaded in the main thread, would it
>>>> be available to a
>>>> worker for use in rendering?
>>> Not without some pretty serious reworking. Which might need to happen.
>>> Of course basic text layout would also not be available without some
>>> serious reworking (e.g. making the textrun cache threadsafe or
>>> creating per-thread textrun caches or something), so the question of
>>> web fonts is somewhat academic at the moment.
>> I meant solely for Canvas 2d.
> Yes, I understand that.  Canvas 2d text still needs to be able to do 
> things like font fallback, shaping, bidi, etc, etc, etc. last I checked.

Oh, the rendering isn't thread safe either? Yes, Canvas 2d text does [is 
supposed to] use all of those items.

Well, I'll give up strokeText/fillText entirely in workers if it'll get 
me the goods faster.
For a11y, I'm going to need to track my text in the main thread anyway. 
I can pre-render there if need be.

Received on Tuesday, 15 May 2012 02:33:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC