Intent to implement: Remove plugin exception for tiny content

26320 views
Skip to first unread message

Rachel Blum

unread,
May 25, 2016, 1:53:14 PM5/25/16
to Chromium-dev, Ryan Schoen


Contacts

Eng: gr...@chromium.org

PM: rsc...@chromium.org


Summary

In September 2015, we made "Detect and run important plugin content" the default plugin setting in Chrome, automatically pausing any cross-origin plugin content smaller than 400px in width or 300px in height. This behavior has an exception for any plugin content that is 5x5 or smaller or is an undefined size, because there was no canonical way of detecting viewability until Intersection Observer was standardized and implemented.


We would now like to remove this exception and instead not load tiny, cross-origin content. If the user has their plugin setting set to the default of "Detect and run important plugin content", the browser will not instantiate cross-origin plugin content that is roughly 5x5 or smaller or has an undefined size. An icon will be displayed in the URL bar indicating that plugin content is not running, allowing the user to reload the page with plugin content running or open settings to add a site-wide exception. Other choices of the plugin content setting are unaffected by this launch.


For more details, see the design doc.


Spec

The behavior of plugin content is not standardized, but this removal is designed to move toward a more standards-based approach. It is a follow-on to intersection observer, which implements a standardized version of the viewability detection, a very common use case for this tiny cross-origin plugin content.


Brett Wilson

unread,
May 25, 2016, 1:56:01 PM5/25/16
to Rachel Blum, Chromium-dev, Ryan Schoen
Hooray!

Brett

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Stefan Zager

unread,
May 25, 2016, 2:08:30 PM5/25/16
to gr...@chromium.org, Chromium-dev, Ryan Schoen
Yay!

Comments are not enabled on the design doc, so here are a couple of questions:

- How confident are you that *all* tiny plugin content is functionally replaceable by IntersectionObserver?
- Do you have a timeframe for doing this?  IntersectionObserver is in M51, which is maybe just beginning to hit stable, and the polyfill is not done.  We probably ought to let it bake a bit and give developers some time to start using it.


--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

PhistucK

unread,
May 25, 2016, 4:01:03 PM5/25/16
to Stefan Zager, Rachel Blum, Chromium-dev, Ryan Schoen

On Wed, May 25, 2016 at 9:07 PM, 'Stefan Zager' via Chromium-dev <chromi...@chromium.org> wrote:
- How confident are you that *all* tiny plugin content is functionally replaceable by IntersectionObserver?

Sounds like this is the only use case that caused it not to be blocked in the first place. Any other use case does not matter, like the rest of the 6x6 - 400x300​ cross origin Flash objects. The user can start them anyway, so this is not a big deal.



PhistucK

Stefan Zager

unread,
May 25, 2016, 4:15:54 PM5/25/16
to PhistucK, Rachel Blum, Chromium-dev, Ryan Schoen
OK, but with this change, "tiny" plugin content would *never* run.  There would be no "play" button or any other way for the user to allow it to run.  It would be effectively banned in all circumstances.  That's very different from the current treatment of medium-sized plugin content.

PhistucK

unread,
May 25, 2016, 4:18:19 PM5/25/16
to Stefan Zager, Rachel Blum, Chromium-dev, Ryan Schoen
Just like 6x6 content - was 6x6 content able to run?


PhistucK

Joe Mason

unread,
May 25, 2016, 4:26:23 PM5/25/16
to sza...@google.com, PhistucK, Rachel Blum, Chromium-dev, Ryan Schoen
The first post in the thread mentions an icon in the url bar to allow plugins with no visible target to run.

Stefan Zager

unread,
May 25, 2016, 5:27:52 PM5/25/16
to Joe Mason, PhistucK, Rachel Blum, Chromium-dev, Ryan Schoen
On Wed, May 25, 2016 at 1:25 PM Joe Mason <joenot...@chromium.org> wrote:
The first post in the thread mentions an icon in the url bar to allow plugins with no visible target to run.

Ah, I see you're right; I think that's just missing from the design doc.

Rachel Blum

unread,
May 25, 2016, 6:14:58 PM5/25/16
to Stefan Zager, Joe Mason, PhistucK, Chromium-dev, Ryan Schoen
See section "UI treatment" :) (Granted, docs wordbreaks the crucial content on the next page...)

Eltoro Pepe

unread,
Aug 10, 2016, 2:19:13 AM8/10/16
to Chromium-dev, rsc...@chromium.org

Michał Gołębiowski

unread,
Aug 28, 2016, 4:10:51 PM8/28/16
to Chromium-dev, rsc...@chromium.org
The code handling tiny content is still there even on master; has the decision been delayed?

wax miguel

unread,
Aug 31, 2016, 10:10:58 AM8/31/16
to Chromium-dev, rsc...@chromium.org

swapna iyer

unread,
Sep 27, 2016, 3:49:23 PM9/27/16
to Chromium-dev, rsc...@chromium.org
Hi,

The design doc does not talk about plugins which do not have a defined size or are not viewable. What happens in those cases? From the explanation here, it seems like, they will be blocked and there will not be a way to load them, unless user chooses to re-load the whole page with 'all plugins enabled'. Is that correct? 

I am interested in knowing about analytics plugins, which do not occupy any space on the DOM. 

Thanks,
Swapna


On Wednesday, May 25, 2016 at 10:53:14 AM UTC-7, Rachel Blum wrote:

Octavian Naicu

unread,
Sep 28, 2016, 4:25:59 AM9/28/16
to Chromium-dev, rsc...@chromium.org
Is it not clear from the 1st post in this thread?

the browser will not instantiate cross-origin plugin content that is roughly 5x5 or smaller or has an undefined size

Ryan Schoen

unread,
Sep 28, 2016, 9:45:24 AM9/28/16
to swapna iyer, Chromium-dev
Hi Swapna,

Yes, your understanding is correct. Those plugins will be blocked and the only way to load them is if the user takes an action to enable plugins.

Thanks,
Ryan

swapna iyer

unread,
Sep 28, 2016, 1:00:47 PM9/28/16
to Ryan Schoen, Chromium-dev
Ryan, Thank you!

Rob McQuaid

unread,
Oct 19, 2019, 1:36:04 PM10/19/19
to Chromium-dev, rsc...@chromium.org
Something else is replacing it right? and how do we get it? what is it? im kinda confused

PhistucK

unread,
Oct 19, 2019, 2:23:00 PM10/19/19
to robmcqu...@gmail.com, Chromium-dev, Ryan Schoen
For the viewability tracking use case, yes, there is a JavaScript based replacement -  intersection observer.
What other use cases do you have that cannot be achieved without Flash?

PhistucK


--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

george ehrlinger

unread,
Mar 18, 2020, 4:24:45 PM3/18/20
to Chromium-dev, rsc...@chromium.org


On Wednesday, May 25, 2016 at 1:53:14 PM UTC-4, Rachel Blum wrote:

george ehrlinger

unread,
Mar 18, 2020, 4:24:45 PM3/18/20
to Chromium-dev, rsc...@chromium.org


On Wednesday, May 25, 2016 at 1:53:14 PM UTC-4, Rachel Blum wrote:

المعلمة الصغيرة

unread,
Aug 14, 2020, 8:09:37 PM8/14/20
to Chromium-dev, rsc...@chromium.org

المعلمة الصغيرة

unread,
Aug 14, 2020, 8:10:00 PM8/14/20
to Chromium-dev, rsc...@chromium.org


بتاريخ الأربعاء، 25 مايو، 2016 7:53:14 م UTC+2، كتب Rachel Blum:

المعلمة الصغيرة

unread,
Aug 14, 2020, 8:10:14 PM8/14/20
to Chromium-dev, rsc...@chromium.org
hèyyy


بتاريخ الأربعاء، 25 مايو، 2016 7:53:14 م UTC+2، كتب Rachel Blum:
Reply all
Reply to author
Forward
0 new messages