On 24/09/14 02:11, Valentin Gosu wrote:
== Test coverage ==
dom/tests/mochitest/general/test_resource_timing.html
dom/tests/mochitest/general/test_resource_timing_cross_origin.html
There is also the w3c test, which presents some failures for all UAs
because of bugs in the test.
Summary: (from the spec) Pages on a single origin opened by the same user in
the same user agent but in different unrelated browsing contexts sometimes need
to send notifications to each other, for example hey, the user logged in over
here, check your credentials again.
For elaborate cases,
On 24 September 2014 12:08, James Graham ja...@hoppipolla.co.uk wrote:
On 24/09/14 02:11, Valentin Gosu wrote:
== Test coverage ==
dom/tests/mochitest/general/test_resource_timing.html
dom/tests/mochitest/general/test_resource_timing_cross_origin.html
There is also the w3c test, which
On 2014-09-23, 7:07 PM, Daniel Holbert wrote:
On 09/23/2014 02:56 PM, Daniel Holbert wrote:
FWIW, I also emailed www-style to sanity-check my understanding to see
if there are any other reasons for this behavior-difference:
http://lists.w3.org/Archives/Public/www-style/2014Sep/0340.html
On 24/09/14 14:27, Valentin Gosu wrote:
On 24 September 2014 12:08, James Graham ja...@hoppipolla.co.uk wrote:
On 24/09/14 02:11, Valentin Gosu wrote:
== Test coverage ==
dom/tests/mochitest/general/test_resource_timing.html
On Tuesday 2014-09-23 17:15 -0700, Justin Dolske wrote:
On 9/23/14 4:24 PM, Jonas Sicking wrote:
This makes the implementation considerably simpler, which is great. It
also means that pixelated will essentially just be a
more-interoperable version of -moz-crisp-edges, for the time being.
Yes!
Though as previously expressed, I don't think we should ship this until it
supports sending Blobs.
But we should definitely land preffed off as soon as patches are reviewed.
/ Jonas
On Sep 24, 2014 3:45 AM, Andrea Marchesini amarches...@mozilla.com
wrote:
Summary: (from the spec) Pages
On 09/24/2014 07:38 AM, Ehsan Akhgari wrote:
This makes the implementation considerably simpler, which is great. It
also means that pixelated will essentially just be a
more-interoperable version of -moz-crisp-edges, for the time being.
So, what are we planning to do with -moz-crisp-edges?
Hey folks,
We already have the protobuf library in the tree, and it seems to be
used for layer scope and webrtc.
I'd like to use it for serializing heap snapshots in devtools code, but
I have a couple questions:
* How do I integrate the compilation of the message description (.proto
file)
On Wed, Sep 24, 2014 at 7:21 PM, Daniel Holbert dholb...@mozilla.com
wrote:
On 09/24/2014 07:38 AM, Ehsan Akhgari wrote:
This makes the implementation considerably simpler, which is great. It
also means that pixelated will essentially just be a
more-interoperable version of
- Original Message -
Hey folks,
We already have the protobuf library in the tree, and it seems to be
used for layer scope and webrtc.
I'd like to use it for serializing heap snapshots in devtools code, but
I have a couple questions:
* How do I integrate the compilation of the
The Web APIs documentation meeting is Friday at 10 AM Pacific Time (see
http://bit.ly/APIdocsMDN for your time zone). Everyone's welcome to
attend; if you're interested in ensuring that all Web APIs are properly
documented, we'd love your input.
We have an agenda, as well as details on how to
On 09/24/2014 09:32 AM, L. David Baron wrote:
Or, alternatively, it seems like the use case here would be
addressed by doing what the spec said before.
Following up more on this: the CSSWG has now resolved to *allow* (but
not require) the formerly-required-by-spec prettier downscaling
On 2014-09-24, 9:12 PM, Daniel Holbert wrote:
On 09/24/2014 09:32 AM, L. David Baron wrote:
Or, alternatively, it seems like the use case here would be
addressed by doing what the spec said before.
Following up more on this: the CSSWG has now resolved to *allow* (but
not require) the
On 09/24/2014 06:26 PM, Ehsan Akhgari wrote:
Hmm, doesn't that basically allow non-interoperable implementations? :(
I think Jonas' idea on having separate properties for the upscale vs.
downscale cases is much better.
I'm unconvinced about the usefulness of exposing that much control. This
On 09/24/2014 09:23 PM, Daniel Holbert wrote:
So, it's not required to behave exactly the same everywhere; it simply
codifies an author's intent. (OK, I suppose it *is* required to behave
exactly the same everywhere in the case of pixelated upscaling,
since that requires a particular
16 matches
Mail list logo
