- From: Justin Novosad <junov@google.com>
- Date: Mon, 10 Mar 2014 14:38:37 -0400
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Dirk Schulze <dschulze@adobe.com>, "whatwg@whatwg.org" <whatwg@whatwg.org>, Joe Gregorio <jcgregorio@google.com>
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier <cabanier@gmail.com> wrote: > On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio <jcgregorio@google.com > >wrote: > > > > > What part is slow, the decoding and re-encoding, or is just always the > > encoding step > > that is slow? > > > > It's decoding/re-encoding of an already constructed path. Can't the implementation just perform that work lazily the first time the path is rasterized, and retain the cached result for subsequent use of the path object?
Received on Monday, 10 March 2014 18:39:03 UTC