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

Issue 670011 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 600630
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Cut off for extension icons didn't sync to ChromeOS

Project Member Reported by rpop@google.com, Nov 30 2016

Issue description

Chrome Version: 54.0.2840.101 (Official Build) (64-bit)
OS: ChromeOS

What steps will reproduce the problem?
(1) Have a bunch of extensions on Mac/Windows
(2) On Mac/Windows, drag the right side of the omnibox rightward to hide some extensions
(3) Sign in to a new ChromeOS device

What is the expected result?
Extensions that were previously hidden from the omnibox row are still hidden

What happens instead?
All extensions are showing up

Possible confounding factor: this is an enterprise-managed ChromeOS machine with https://chrome.google.com/webstore/detail/google-corporate-chrome-o/inmdanhiiibfpdlljnjjbchhjgelojnn force-installed. Perhaps that is what triggered showing all extensions and there is no sync issue.
 

Comment 1 by rpop@chromium.org, Nov 30 2016

Cc: rpop@chromium.org

Comment 2 by jawag@chromium.org, Nov 30 2016

I don't think Chrome syncs this yet. Copy/paste from a separate thread:

No, Chrome doesn't sync this yet. Feel free to weigh in at  https://crbug.com/600630 . The question of how to sync this information is tricky, because it also determines the width of the omnibox, which isn't something we would want to sync between devices with drastically different screen sizes.

I believe we do sync the order of the icons. So on a new machine, all you should have to do is resize the omnibox (click and drag between the omnibox and the extension icons) which will push icons on the right into the Chrome menu.

Comment 3 by jawag@chromium.org, Nov 30 2016

Mergedinto: 600630
Status: Duplicate (was: Unconfirmed)
Merging this into the aforementioned bug.

Sign in to add a comment