Interventions: updates since 5/9/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 5/9/2017

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

agreed to try shipping it on m59 through the finch if metrics are fine

Next Steps:

wait for metrics of m59 stable that contains the last metrics change

Link(s): spec/discussion implementation


Data Saver and autoplay video
Engineer(s): mlam...@google.com
Status as of 5/10/2017

TBD

Next Steps:

meeting the 2017-05-12

Cancel modal dialogs on tab switch and don't allow them for background pages ("Project OldSpice")
Engineer(s): a...@google.com
Status as of 5/10/2017

Turned on everywhere

Next Steps:

Remove the flag (which several people need because there are bugs that only repro with old dialogs), close out all the dialog bugs addressed.

Link(s): implementation


only allow beforeunload dialogs on frames that have had a user gesture
Engineer(s): a...@google.com
Status as of 5/10/2017

Landed in M60.

Next Steps:

There is a followup issue where a keyboard command to close or reload could be mistaken for a user gesture. Working on that.

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.