On 8/17/2016 5:03 PM, Karl Dubost wrote:
Chris,
Le 18 août 2016 à 02:21, Chris Peterson <cpeter...@mozilla.com> a écrit :
Here is a status report from the Chrome team about their current and future
"interventions":
https://docs.google.com/document/d/1vqM_Dbi-V7LtdOwb2IGjgor9Fvl5k_FvO2DJGr4CaSQ/
An intervention is when a user agent decides to deviate slightly from a
standardized behavior in order to provide a greatly enhanced user experience.
Very cool information. Two thoughts.
1. What is the status report about Firefox "interventions"
AFAIK, we don't have a coordinated plan for interventions. I know we
have already shipped some iframe and timer throttling and we are now
testing blocking of non-essential plugin content in Beta 49:
https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/
2. What are the impact of the Chrome "interventions" on Firefox Web
compatibility (aka if they change the behavior and developers adjust to the new black,
will it break in Firefox).
The following presentation from the Chrome team's BlinkOn 6 talks about
some of the behavior changes and some of their decision-making process
when designing interventions. One unfortunate example, advertisers
worked around Chrome for Android's "do not autoplay mobile videos"
intervention by deploying pseudo-video ads using canvas-based video
codecs, which was worse for bandwidth and power usage.
https://youtu.be/wQGa_6CRc9I
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
