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

Issue 753314 link

Starred by 1 user
Status: Duplicate
Merged: issue 638375
Owner:
piman@chromium.org
Closed: Aug 2017
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Iframe created by browser extension fails to appear

Reported by robertkn...@hypothes.is, Aug 8 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.1.2 Safari/603.3.8

Steps to reproduce the problem:
1. Install the extension from https://github.com/hypothesis/chrome-invisible-iframe-bug (or the attached tarball)
2. Open a new tab at http://example.org (or any other URL) and click the toolbar icon to activate the extension
3. Click the link in the yellow iframe that appears in the page
4. Click the toolbar icon to activate the extension in the new tab

What is the expected behavior?
The yellow frame should appear in the second tab that was opened.

What went wrong?
The iframe's outline appears but the contents are invisible. A tarball of the extension is attached.

Note that it appears to be important that the second tab is *opened by clicking the link in the iframe*.

This is a reduced test case for an issue originally reported at https://github.com/hypothesis/client/issues/516

WebStore page: https://github.com/hypothesis/chrome-invisible-iframe-bug

Did this work before? N/A 

Chrome version: 	62.0.3175.4  Channel: dev
OS Version: OS X 10.12.6
Flash Version: 

Tested in Chrome 62.0.3175.4 and 62.0.3179.0 on macOS.
extension.tar.gz
13.2 KB Download

Comment 1 by ligim...@chromium.org, Aug 8 2017

Labels: -Pri-2 Needs-Triage-M62 Needs-Bisect Pri-1

Comment 2 by hdodda@chromium.org, Aug 9 2017

Cc: hdodda@chromium.org
Labels: -Type-Bug -Needs-Bisect hasbisect-per-revision M-62 OS-Linux OS-Windows Type-Bug-Regression
Owner: piman@chromium.org
Status: Assigned (was: Unconfirmed)
Tested the issue on windows 7 , ubuntu 14.04 and mac os 10.12.6 using chrome M60 #60.0.3112.90 and M62 #62.0.3179.0 and issue is reproduced.

This is a regression issue broken in M59.

Using the per-revision bisect providing the bisect results,
Good build: 59.0.2961.0 (Revision: 461353).
Bad build: 59.0.2963.0 (Revision: 461928).

You are probably looking for a change made after 461458 (known good), but no later than 461459 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspectas some perf builds might get missing due to failure.

 https://chromium.googlesource.com/chromium/src/+log/910b408e9d1ba5c36b5663a682b70cfc43e58a53..00cf9403c34aea924ffecd736f93e06421e10e15

From the CL above, assigning the issue to the concern owner 

@piman- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Review-Url: https://codereview.chromium.org/2496233003

Thanks!

Comment 3 by piman@chromium.org, Aug 9 2017

Mergedinto: 638375
Status: Duplicate (was: Assigned)
►

Sign in to add a comment