On Thu, Jul 3, 2014 at 3:03 AM, Justin Novosad wrote:
> On Fri, Jun 27, 2014 at 6:42 PM, Robert O'Callahan
> wrote:
> This behavior seems sound at first glance, but because that arithmetic may
> >> induce a change to the intrinsic aspect ratio due to rounding, step 3)
> may
> >> not jump out of
On Wed, 2 Jul 2014, Rik Cabanier wrote:
>
> The canvas spec [1] currently states:
>
> If any of the following conditions are met, throw a NotSupportedError
> exception and abort these steps:
>
> ...
>
> The specified pixels has no pixels.
>
>
> Since the specified pixels are the union of the c
The canvas spec [1] currently states:
If any of the following conditions are met, throw a NotSupportedError
exception and abort these steps:
...
The specified pixels has no pixels.
Since the specified pixels are the union of the clipping path and the
current path, it will be nearly impossible
On Wed, Jul 2, 2014 at 9:27 PM, Boris Zbarsky wrote:
> On 7/2/14, 3:21 PM, Rik Cabanier wrote:
>
>> facts = 2 implementations. I certainly didn't say anything else.
>>
>
> You said, and I quote:
>
>
> That thread concluded with a "let's see how this feature is going to
> be used before we com
On 7/2/14, 3:21 PM, Rik Cabanier wrote:
facts = 2 implementations. I certainly didn't say anything else.
You said, and I quote:
That thread concluded with a "let's see how this feature is going to
be used before we commit".
Anyway, 2 implementations is a necessary condition for a REC, not
On Wed, Jul 2, 2014 at 9:04 PM, Joshua Cranmer
wrote:
> On 7/2/2014 8:31 AM, Rik Cabanier wrote:
>
>> That thread concluded with a "let's see how this feature is going to be
>> used before we commit". Blink and WebKit certainly are in favor.
>>
>
> I went back and looked at the later messages in
On 7/2/2014 8:31 AM, Rik Cabanier wrote:
That thread concluded with a "let's see how this feature is going to
be used before we commit". Blink and WebKit certainly are in favor.
I went back and looked at the later messages in that thread. Your
argument implies that a plurality of engines impl
On Wed, Jul 2, 2014 at 11:31 AM, Rik Cabanier wrote:
> I thought that those concerns were addressed with the addition of a maximum
>
number of cores?
>
That doesn't address much, if anything.
> > Also, WebKit's implementation also caps the number of cores at eight
> > to mitigate some of the f
On Wed, Jul 2, 2014 at 6:00 PM, Ryosuke Niwa wrote:
> On Jul 2, 2014, at 6:31 AM, Rik Cabanier wrote:
>
>
> On Wed, Jul 2, 2014 at 10:37 AM, Anne van Kesteren
> wrote:
>
>> On Wed, Jul 2, 2014 at 8:58 AM, Rik Cabanier wrote:
>> > Since there are now 2 implementations, it should be added to the
On Jul 2, 2014, at 6:31 AM, Rik Cabanier wrote:
>
> On Wed, Jul 2, 2014 at 10:37 AM, Anne van Kesteren wrote:
> On Wed, Jul 2, 2014 at 8:58 AM, Rik Cabanier wrote:
> > Since there are now 2 implementations, it should be added to the spec
> > instead of just being a wiki.
>
> That depends on w
On Fri, Jun 27, 2014 at 6:42 PM, Robert O'Callahan
wrote:
> On Sat, Jun 28, 2014 at 3:41 AM, Justin Novosad wrote:
>
>> Example of a problematic renderedsizechange event listener:
>>
>> canvas.width = Math.floor(canvas.renderedPixelWidth * myPixelScale);
>> canvas.height = Math.floor(canvas.rend
On Wed, Jul 2, 2014 at 3:31 PM, Rik Cabanier wrote:
> That thread concluded with a "let's see how this feature is going to be used
> before we commit".
I cannot find that quote.
--
http://annevankesteren.nl/
On Wed, Jul 2, 2014 at 10:37 AM, Anne van Kesteren wrote:
> On Wed, Jul 2, 2014 at 8:58 AM, Rik Cabanier wrote:
> > Since there are now 2 implementations, it should be added to the spec
> > instead of just being a wiki.
>
> That depends on whether other vendors are objecting.
>
> Looks like that
On 2 July 2014 03:18, Ryosuke Niwa wrote:
>
> Could you point me to a specific test case that demonstrates the
difference?
Sure, here you go:
https://people.mozilla.org/~bowen/openerTest/openerTest.html
In IE you get "firstOpener" alerted both times, which is as spec.
In Firefox and Chrome "sec
On Wed, Jul 2, 2014 at 8:58 AM, Rik Cabanier wrote:
> Since there are now 2 implementations, it should be added to the spec
> instead of just being a wiki.
That depends on whether other vendors are objecting.
Looks like that is the case:
https://groups.google.com/d/msg/mozilla.dev.platform/QnhfU
15 matches
Mail list logo
