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

Issue 634309 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Page not loading after clicking on reload button and showing error "Plug-in blocked" error in chrome://chrome-signin page in Emulation

Project Member Reported by susanjun...@techmahindra.com, Aug 4 2016

Issue description

Version: 54.0.2817.0
OS: Ubuntu 14.04, Windows

What steps will reproduce the problem?
(1)Launch Chrome and go to chrome://chrome-signin page.
(2)Click F12 to open Dev tools and click on Toogle device toolbar.
(3)Click on reload button and observe. Page is not loading and showing the error "Plug-in blocked".(Refer actual and expected videos).

Expected: Chrome Signin page should reload in Emulation mode.
Actual: Instead, Chrome Signin page is not getting reloaded.

This is a regression issue broken in M-49.

Manual good and Bad Builds:
Good Build: 49.0.2566.0
Bad Build:  49.0.2567.0

Below is the Manual Bisect Info:
CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/49.0.2566.0..49.0.2567.0?pretty=fuller&n=10000

Change log from Windows: http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&range=360161%3A360171

Unable to find the Suspect from the above Change log. Someone from Dev team please look into the issue


 
actual_signin_screen.ogv
833 KB View Download
Expected_signin_screen.ogv
1.7 MB View Download
Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Mac OS 10.11.6 using chrome latest Dev #54.0.2817.0. 
Owner: dgozman@chromium.org
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
This is expected - we disable plugins when emulating mobile device.

Sign in to add a comment