Thanks, Tobias. If all goes well, please request uplift to FF 54 for
this after a few days in Nightly 55 to unblock bugs like:
https://bugzilla.mozilla.org/show_bug.cgi?id=1131937#c28
--Jet
On Wed, Apr 5, 2017 at 2:21 PM, Tobias Schneider wrote:
> Out final experiment on 100% of our Nightly user
Out final experiment on 100% of our Nightly user population just finished.
We enabled the API for 110605 users. Out of that we only had 2 reported
crashes related to the Intersection Observer API. Both were causes by
Add-ons using the API in XUL documents. We already addressed this issue in
https:
We just successfully run another experiment, enabling the
IntersectionObserver API for 50% of our Nightly user population. No related
stability issues reported. Also, find a Gecko profile using an Intersection
Observer per element (109192 total) on the single page version of the HTML5
spec here:
ht
>
> 1) Is there devtools support for this (e.g. to be able to see what
> intersection observers are registered where)? If not, are there at least
> bugs tracking it?
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1347849 for this.
MutationObserver would be a good one to add support for to
On Wed, Mar 15, 2017 at 7:38 PM, Boris Zbarsky wrote:
> On 3/15/17 1:32 PM, Tobias Schneider wrote:
>> 2.3) Platform tests are in the process of being upstreamed by Google (
>> https://github.com/w3c/web-platform-tests/pull/4384).
>
> That seems to be in limbo for well over a month now. jgraham j
On 2017-03-15 1:32 PM, Tobias Schneider wrote:
2.2) No signals from Safari that I know of.
Simon Fraser has implemented part of it in
https://bugs.webkit.org/show_bug.cgi?id=159475 , but things appear to
have stalled. He also filed quite a few spec bugs in the process:
https://github.com/WIC
On 3/15/17 1:32 PM, Tobias Schneider wrote:
1) No there isn't any yet. Good idea to file a bug for it tho.
OK. Please make sure this happens.
2.1) Its was quite a living spec over the time I implemented things, but
stuff seams to stabilize now.
https://bugzilla.mozilla.org/show_bug.cgi?id=12
As of March 14 I intend to turn the IntersectionObserver API on by default
on all platforms. It has been developed behind the
dom.IntersectionObserver.enabled preference. Chrome is already shipping it
since 51.
Manual QA and fuzzing was successfully completed (
https://wiki.mozilla.org/QA/Intersec
1) No there isn't any yet. Good idea to file a bug for it tho.
2.1) Its was quite a living spec over the time I implemented things, but
stuff seams to stabilize now.
https://bugzilla.mozilla.org/show_bug.cgi?id=1243846 is tracking bug for
spec changes that we haven't addressed yet.
2.2) No signal
On 3/15/17 1:30 AM, Tobias Schneider wrote:
As of March 14 I intend to turn the IntersectionObserver API on by default
on all platforms.
This is really exciting stuff!
Some questions (largely based on the intent to ship/implement templates,
fwiw):
1) Is there devtools support for this (e.g
On 2017-03-15 8:14 AM, Michael de Boer wrote:
> Hi Tobias,
>
> Very exciting! This is a _very_ welcome addition to the family of Web APIs,
> IMHO.
>
> I’m curious about the performance characteristics for consumers of this API:
> how does it scale in respect to
> 1. The amount of observers acti
Hi Tobias,
Very exciting! This is a _very_ welcome addition to the family of Web APIs,
IMHO.
I’m curious about the performance characteristics for consumers of this API:
how does it scale in respect to
1. The amount of observers active on a single page and
2. Size of the page in raw DOM node co
As of March 14 I intend to turn the IntersectionObserver API on by default
on all platforms. It has been developed behind the
dom.IntersectionObserver.enabled
preference. Chrome is already shipping it since 51.
Manual QA and fuzzing was successfully completed (
https://wiki.mozilla.org/QA/Intersec
13 matches
Mail list logo
