On Sun, Mar 9, 2014 at 10:52 PM, Dirk Schulze dschu...@adobe.com wrote:
On Mar 10, 2014, at 3:44 AM, Rik Cabanier caban...@gmail.com wrote:
On Wed, Mar 5, 2014 at 1:46 PM, Rik Cabanier caban...@gmail.com
wrote:
While implementing the Path2D object in mozilla, we ran into a
On Mon, Mar 10, 2014 at 2:02 PM, Rik Cabanier caban...@gmail.com wrote:
What are you not sure about?
The current Path2D interface might be unacceptably slow under certain
circumstances and there's currently no way for authors to work around this.
There has to be a hint. If not, I don't see
On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio jcgrego...@google.comwrote:
On Mon, Mar 10, 2014 at 2:02 PM, Rik Cabanier caban...@gmail.com wrote:
What are you not sure about?
The current Path2D interface might be unacceptably slow under certain
circumstances and there's currently no
On Mar 10, 2014, at 7:02 PM, Rik Cabanier caban...@gmail.com wrote:
On Sun, Mar 9, 2014 at 10:52 PM, Dirk Schulze dschu...@adobe.com wrote:
On Mar 10, 2014, at 3:44 AM, Rik Cabanier caban...@gmail.com wrote:
On Wed, Mar 5, 2014 at 1:46 PM, Rik Cabanier caban...@gmail.com
wrote:
What about making the Path2D constructor a property of each context? E.g.
var path = new myContext.Path2D(...);
Each context would have a different constructor tied to it, allowing this kind
of optimization.
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio jcgrego...@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
On Tue, 7 Jan 2014, Yoav Weiss wrote:
On Tue, Jan 7, 2014 at 6:20 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/7/14 12:01 PM, Yoav Weiss wrote:
I'd love to get some more details regarding that. I'll start a
mozilla.dev.platform thread on the subject, since it's Gecko
specific.
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad ju...@google.com wrote:
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio jcgrego...@google.com
wrote:
What part is slow, the decoding and re-encoding, or is just always the
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad ju...@google.com wrote:
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio jcgrego...@google.com
wrote:
What part is slow, the decoding and re-encoding, or is just
Hi WhatWG.
Currently, requestAutocomplete lets a user agent provide the same user
experience across multiple sites for common data input flows. A site
describes the data it desires (via a form and autocomplete attributes), and
the user agent uses this information and what it knows about the user
On Mon, Mar 10, 2014 at 4:22 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad ju...@google.com wrote:
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio jcgrego...@google.com
On Mon, Mar 10, 2014 at 1:33 PM, Justin Novosad ju...@google.com wrote:
On Mon, Mar 10, 2014 at 4:22 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad ju...@google.comwrote:
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier
Currently, the specification states that if you create a region and then
create another region that completely covers region, the first region is
removed from the hit region list [1]
This is a complex operation that involves either drawing the regions to a
bitmaps and counting pixels, or path
clearRect is currently defined as a subtraction mechanism for hit regions
[1].
It's unlikely that a UA will implement hit regions using pixels so this
would have to be done using path subtraction which is expensive.
Why was this special behavior added to clearRect? Hit regions are not
subject to
On Mar 7, 2014, at 3:54 AM, Smylers smyl...@stripey.com wrote:
Ryosuke Niwa writes [re-ordered]:
On Feb 19, 2014, at 7:36 AM, Jukka K. Korpela jkorp...@cs.tut.fi
wrote:
2014-02-19 11:10, Smylers wrote:
Jukka K. Korpela writes:
The point is that year numbers aren't really numbers in
15 matches
Mail list logo
