Interventions: updates since 6/13/2017

[kenji...@chromium.org]

This email has been automatically sent by a script (got feedback?)
What are interventions?
An Intervention is when a Browser opts for:

• an intentional deviation from a behavior that developers expect and/or rely on,
• which is motivated by the desire to fulfill an important user need.

Because of its nature, it must be done sparingly and with extreme care to not only achieve but also sustain a positive outcome.


Updates for interventions since 6/13/2017

Don't load slow web fonts (using NQE)
Engineer(s): tba...@google.com, toyo...@google.com
Status as of 6/16/2017

Running in M-59+ Canary/Dev/Beta. Approved for M-59 1% stable. Limited data from M-59+ Canary/Dev/Beta looks positive with 8% reduction in median time to first text paint on 2G and 3G connection types.

Next Steps:

Wait for data from 1% stable M-59.

Link(s): spec/discussion implementation


Defer cross-origin iframe loads until they are viewable (add a lazyload attribute to give developer control?)
Engineer(s): be...@google.com
Status as of 6/16/2017

collecting data on WebpageTest

Next Steps:

Analyze data use savings, fix memory experiments, collect more data.

Link(s): spec/discussion implementation




Full details for all the interventions can be found at bit.ly/proposed-interventions.
See also, WICG interventions: a place for browsers to collaborate on browser interventions.
Tell us how useful these updates are and how we could improve them by sharing your feedback.