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

Issue 696368 link

Starred by 2 users
Status: Duplicate
Merged: issue 690523
Owner:
█ ackermanb@chromium.org
Last visit 28 days ago
Closed: Feb 2017
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

In-line extensions do not begin installation process when Chrome window is in full screen mode on MAC

Reported by linye.zh...@gmail.com, Feb 26 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Change Chrome window to full screen mode
2. Visit Joinhoney.com, Grammarly.com, or any website with in-line extension
3. Try to install extension

What is the expected behavior?
Chrome installation modal appears

What went wrong?
Chrome installation modal does not appear

WebStore page: 

Did this work before? Yes 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.10.5
Flash Version:

Comment 1 by nyerramilli@chromium.org, Feb 27 2017

Labels: Needs-Bisect Needs-Triage-M56

Comment 2 by hdodda@chromium.org, Feb 27 2017

Cc: hdodda@chromium.org
Labels: Needs-Feedback
Tested on Mac OS 10.12.2 using chrome M56 #56.0.2924.87 and followed steps below:

1. Launched chrome and changed to full screen mode .
2. Navigated to joinhoney.com and installed honey extension and installation successful and is redirected to joinhoney.com website.

Attached screencast for reference.

@linye.zhang18-- Could you please check attached screencast and confirm us if we had followed correct steps in reproducing the issue , if not , please helps us in reproducing the issue by providing the screencast.

Thanks!
696368.mp4
1.8 MB View Download

Comment 3 by do...@blackcart.co, Feb 27 2017 

@hdodda, you'll need to click on the inline button on the joinhoney.com webpage. Please take a look at the screencast attached.
Screen Capture on 2017-02-27 at 04.12.43.1.mov
17.2 MB Download

Comment 4 by hdodda@chromium.org, Feb 28 2017

Labels: -Needs-Feedback -Needs-Bisect -Needs-Triage-M56 hasbisect-per-revision M-56
Owner: ackermanb@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 56.0.2886.0 (Revision: 424099).
Bad build: 56.0.2887.0 (Revision: 424315).

You are probably looking for a change made after 424253 (known good), but no later than 424254 (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/e8a19cea39a641c9e35ab84bb621c4246883de7b..6ca20846938a643f34ea9ead734c81c4c6ebd74b

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

@ackermanb - 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/2391353003

Note : Issue is not seen on latest canary and dev versions. and also not seen on windows and linux os.

Thanks!

Comment 5 by ackermanb@chromium.org, Feb 28 2017

Mergedinto: 690523
Status: Duplicate (was: Assigned)
This popped up in  bug 690523  and a fix was merged into M57.
►

Sign in to add a comment