Interventions: updates since 4/18/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 4/18/2017

Look into pausing offscreen muted autoplayed videos.
Engineer(s): mlam...@google.com
Status as of 4/19/2017

Done

Next Steps:

Make touch events uncancelable on unresponsive pages
Engineer(s): tdre...@google.com
Status as of 4/18/2017

Tabled until we can perform touch action hit testing on the compositor thread. (crbug.com/318381)

Next Steps:

Implement touch action hit testing. This could be a while, as it's all mixed up with slimming paint work.

Link(s): implementation


disallow top-level navigations to blob/data urls
Engineer(s): mea...@google.com, dch...@google.com
Status as of 4/24/2017

Blockage CL landed: https://codereview.chromium.org/2702503002/

Next Steps:

Keep an eye on the developer feedback and determine if the blockage needs to be merged to M59. Risks/concerns:
We initially wanted to allow data URL navigations if the top frame is already a data URL. This turned out to be non-trivial as there isn't a reliable way of getting navigation initiator information: crbug.com/651895
As a result, we ended up with blocking data URL to data URL navigations. This might cause slightly larger breakage then expected.

Link(s): 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.