Intend to extend experiment: Long Animation Frame Timing

[Noam Rosenthal]

Contact emails

nrose...@chromium.org

Explainer

https://github.com/w3c/longtasks/blob/main/loaf-explainer.md

Specification

https://github.com/w3c/longtasks/blob/main/loaf-explainer.md

Summary

We propose extending the "Long Animation Frame Timing" experiment.

The experiment has several active participants with multiple URLs, however due to early bugs in the OT implementation (mostly how the origin trial/feature flag logic was configured in chromium) it was out for a slow start.

In addition, it's a "deep" feature with many edge cases, and the origin trial participants are really helping us understand the ins and outs before we ship to a wider audience, but it takes time to reach conclusive feedback.

Proposing to extend it to 3 more milestones, to account for the milestones we lost due to OT churn.

Blink component

Blink>PerformanceAPIs

TAG review

https://github.com/w3ctag/design-reviews/issues/911

TAG review status

Pending

Risks

Interoperability and Compatibility

Gecko: Positive Not yet a formal signal but showed positive interest at WG call.

WebKit: No signal

Web developers: Positive (https://twitter.com/jebbacca/status/1653355406368952321) Wix, Taboola, and others have already experimented with this in Canary. Strong excitement from several partners at We Love Speed conference.

Other signals:

Ergonomics

It should work well with other performance timeline entries, mainly event-timing/INP.

Security

This feature exposes rendering time to iframes, which might be cross-origin (same-process). However, this is anyway observable, by using requestAnimationFrame. Note that everything in this feature is same-process.

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Goals for experimentation

Ongoing technical constraints

None

Debuggability

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes

Flag name

LongAnimationFrameTiming

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1392685

Launch bug

https://launch.corp.google.com/launch/4244858

Estimated milestones

OriginTrial desktop last	123
OriginTrial desktop first	115

OriginTrial Android last	123
OriginTrial Android first	115

OriginTrial webView last	123
OriginTrial webView first	115

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6118675067699200

Links to previous Intent discussions

Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYbX%3DEOAwkEvDQY9Ja1trSXLFtM1XNsuw1Lr2QR88%2BTnqw%40mail.gmail.com

This intent message was generated by Chrome Platform Status.

[Mike Taylor]

Hi Noam,

Ack on the OT bugs (been there...); could you comment on any substantial progress in the following areas:

• Draft spec (early draft is ok, but must be spec-like and associated with the appropriate standardization venue, or WICG)
• TAG review (see exceptions)
• bit.ly/blink-signals requests
• Outreach for feedback from the spec community
• WPT tests

thanks,
Mike

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYaFKKxhZee4q57kfWv6VLq4cru5jV%3Dqv1i%3D9-ojKCDKuQ%40mail.gmail.com.

[Noam Rosenthal]

On Fri, Nov 17, 2023 at 12:28 AM Mike Taylor <mike...@chromium.org> wrote:

Hi Noam,

Ack on the OT bugs (been there...); could you comment on any substantial progress in the following areas:

• Draft spec (early draft is ok, but must be spec-like and associated with the appropriate standardization venue, or WICG)

Not there yet. We wanted to see if the OT was bringing out things that would change the API substantially. So far seems like it doesn't, and writing a draft spec is one of the next things on my agenda.

 

• TAG review (see exceptions)

Posted and assigned, pending: https://github.com/w3ctag/design-reviews/issues/911

 

• bit.ly/blink-signals requests 

Got very good informal signs from the other vendors at TPAC and in other informal conversations. I wanted to wait for a couple of the happy OT participants to provide case studies before I ask for an official standard position. This is also next on the agenda.  

• Outreach for feedback from the spec community

Was discussed several times at WebPerfWG with very good feedback. Can share the link to meeting minutes if requested.

• WPT tests

Very comprehensive: https://wpt.fyi/results/long-animation-frame/tentative?label=experimental&label=master&aligned

 

[Mike Taylor]

Thanks. LGTM to extend 3 more milestones (I believe M121 to M123 inclusive).