Issue metadata
Sign in to add a comment
|
Windows 10 (I guess) border around extension pop-up window on OSX |
|
||||||||||||||||||||||||
| Reported by ninoflo...@gmail.com, Aug 31 2015 | Back to list | |||||||||||||||||||||||||
Issue descriptionUserAgent: 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 faces.im 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 faces.im) 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
,
Aug 31 2015
Able to install extension on Win7 but unable to open the extension.
,
Sep 4 2015
Trent, can you look into this (or punt on to someone else)?
,
Sep 7 2015
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.
,
Sep 9 2015
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/841c14b4ca8818f08890157ba159e331a1995453 commit 841c14b4ca8818f08890157ba159e331a1995453 Author: tapted <tapted@chromium.org> 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 regressions. 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: https://codereview.chromium.org/1329033002 Cr-Commit-Position: refs/heads/master@{#347847} [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/chrome/browser/ui/app_list/search/people/people_result.cc [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/chrome/browser/ui/panels/panel_manager.cc [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/chrome/common/extensions/api/_api_features.json [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/extensions/common/api/_manifest_features.json [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/extensions/common/constants.cc [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/extensions/common/constants.h [modify] http://crrev.com/841c14b4ca8818f08890157ba159e331a1995453/extensions/common/permissions/permissions_data.cc |
||||||||||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||||||||||
Comment 1 by mbollu@chromium.org
, Aug 31 2015Labels: Cr-Platform-Extensions
707 KB View Download