New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 618401 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

cannot inspect properties of <embed> or <object> elements with active flash content

Reported by hu...@cumallover.me, Jun 8 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36

Steps to reproduce the problem:
1. open `page.html` in the attached zip file
2. if plugin placeholders are enabled, select "run this plugin" on the <embed> and <object> elements
3. open the dev tools and select either of the two elements
4. open the "properties" tab in the side menu (or type $0 in the console)

What is the expected behavior?
the element's properties should be visible

What went wrong?
the properties are not visible and the output looks nothing like a typical html element's properties

Did this work before? N/A 

Chrome version: 51.0.2704.79  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

the properties are visible before you do "run this plugin", or if you remove the element's `src` or `data` attribute

i attached a screenshot
 
testcase.zip
40.3 KB Download
screenshot.png
97.9 KB View Download

Comment 1 by l...@chromium.org, Jun 9 2016

Labels: Needs-Bisect OS-Linux
Owner: l...@chromium.org
Status: Untriaged (was: Unconfirmed)
Confirmed on Linux 51.0.2704.84 stable, needs bisect.

Comment 2 by l...@chromium.org, Jun 9 2016

Status: Assigned (was: Untriaged)

Comment 3 by ajha@chromium.org, Jun 10 2016

Cc: gov...@chromium.org ajha@chromium.org l...@chromium.org
Labels: -Type-Bug -Pri-2 -Needs-Bisect ReleaseBlock-Stable M-51 hasbisect OS-Mac Pri-1 Type-Bug-Regression
Owner: kozyatinskiy@chromium.org
Issue is working fine on the latest canary(53.0.2764.0) and the latest beta(52.0.2743.33) on Windows-7, Mac OS 10.11.5 and Linux Ubuntu 14.04. Issue is reproducible only on the latest stable(51.0.2704.84).

Reverse bisected to find the CL that fixed this:

Last bad build:   52.0.2725.0
First good build: 52.0.2726.0

Changelog: https://chromium.googlesource.com/chromium/src/+log/8a350376c9d1d5d00fe1e8d810d0d5167f374c1d..f00e71eb761f55d65e770fcf3dec1c7a28c0ec3f

This would have been fixed by https://codereview.chromium.org/1948583003.

kozyatinskiy@: Could you please review if this is a good candidate to get this merged to M-51, in case there is any stable refresh.

Please adjust the label if this isn't blocking.

Thank you!

Comment 4 by gov...@chromium.org, Jun 12 2016

Cc: pbomm...@chromium.org
Labels: -ReleaseBlock-Stable -M-51
This isn't blocking.
Status: Fixed (was: Assigned)
It's fixed in ToT.

Sign in to add a comment