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

Issue metadata

Status: Duplicate
Merged: issue 467808
Closed: Sep 2015
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Sign in to add a comment

Issue 526708: Windows 10 (I guess) border around extension pop-up window on OSX

Reported by, Aug 31 2015

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2497.0 Safari/537.36

Steps to reproduce the problem:
1. Download an extension that pops open a new window (like a popular facebook messenger integration for chrome)
2. Set it up properly
3. Open the window and see that it's a Windows 10 border

What is the expected behavior?

What went wrong?
When opening a pop-up window through a chrome extension (like this results erroneously in a Windows 10 border, while being on OSX.

Did this work before? Yes v46

Chrome version: 47.0.2497.0  Channel: canary
OS Version: OS X 10.10.4
Flash Version: Shockwave Flash 19.0 r0

Tested in chrome stable where this does not occur
21.2 KB View Download

Comment 1 by, Aug 31 2015

Labels: Cr-Platform-Extensions
OS: Mac 10.10.4
Chrome Version: 44.0.2403.157 stable, 45.0.2454.78 beta, 46.0.2490.6 dev & 47.0.2497.0 canary.

The above mentioned issue reproducible on above M45, M46 & M47 builds but not on M44 build. See attachment. 

Window on left is from M44 build & window on right is from M45, M46 & M47 builds.

Maybe its an extension issue rather than Chrome issue. Adding extension team to see if they can give some inputs.
Screen Shot 2015-08-31 at 12.37.51 PM.png
707 KB View Download

Comment 2 by, Aug 31 2015

Able to install extension on Win7 but unable to open the extension.

Comment 3 by, Sep 4 2015

Status: Assigned
Trent, can you look into this (or punt on to someone else)?

Comment 4 by, Sep 7 2015

Mergedinto: 467808
Status: Duplicate
Likely the behavior in stable depends on the value of chrome://flags/#enable-panels

So the behaviour you're seeing is a direct result of  Issue 467808 . Specifically "PanelManager::ShouldUsePanels() will also allow panels to be created in Chromium builds, and for Dev and Canary official channels." Which is confusing. And a bug. But, like that other issue says, we don't support Panels, and they're likely going away.

Comment 5 by, Sep 9 2015

Project Member
The following revision refers to this bug:

commit 841c14b4ca8818f08890157ba159e331a1995453
Author: tapted <>
Date: Wed Sep 09 00:34:00 2015

Disable extension Panels on Dev and Canary, except for the whitelist

They're already disabled on Beta and Stable channels. Leaving them
enabled in Dev/Canary confuses users and makes people suspect

After this, panels are only enabled when --enable-panels is set in
chrome://flags and for the whitelist (Hangouts).

CL also tries to consolidate all the Hangouts extension IDs scattered
around the codebase.

BUG= 467808 ,  526708 

Review URL:

Cr-Commit-Position: refs/heads/master@{#347847}


Sign in to add a comment