New issue
Advanced search Search tips

Issue 667018 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Blocking plugins by domain doesn't work for iframes

Reported by khym.cha...@gmail.com, Nov 19 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36

Steps to reproduce the problem:
1. In content settings for plugins, set to the recommended "Detect and run important plugin content", and in "Manage exceptions" add a block exception for "[*.]pixiv.net"
2. Browse around pixiv.net for a while with the task manager open, using the task manager to kill the shockwave flash plugin process whenever it appears.

What is the expected behavior?
Absence of evidence that Flash in running on any pixiv.net pages

What went wrong?
Sooner or later you'll see a "Flash has crashed" message at the top of a pixiv.net page.  From what I've been able to determine, the flash is in an iframe with a src under the domain of pixiv.ORG instead of pixiv.NET, and *that* iframe has it's own nested iframe which had no src but did have an id of "google_osd_static_frame" (I'm guessing the nested iframe's src got set programatically from JavaScript).

Did this work before? N/A 

Chrome version: 54.0.2840.100  Channel: stable
OS Version: Fedora 24
Flash Version: Shockwave Flash 23.0 r0
 
Oops, that seemed to have been caused by checking "always allowed to run" in chrome://plugins; unchecking that led to the expected behavior.

Comment 2 by ajha@chromium.org, Nov 21 2016

Labels: M-54

Comment 3 by hdodda@chromium.org, Nov 24 2016

Status: WontFix (was: Unconfirmed)
As per comment #1 , closing this issue. Please feel free to raise a new issue , if you face the issue in latest chrome versions.

Thanks!

Sign in to add a comment