New issue
Advanced search Search tips

Issue 593414 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Pinning profiles no longer results in profile specific pins.

Project Member Reported by gab@chromium.org, Mar 9 2016

Issue description

Version: 50.0.2657.0 canary (64-bit)
OS: Win10

What steps will reproduce the problem?
(1) Create a second profile
(2) Pin its badged window entry to taskbar
(3) Close Chrome

What is the expected output?
Pin remains badged.
Clicking pin launches that profile.

What do you see instead?
Pin is unbadged and clicking it launches "default" (i.e. last profile used).

However we fix this we should probably fix issue 328738 at the same time (decision was taken that window properties should also be profile specific in multi-profile scenarios -- even for the Default profile, i.e. when in multi-profiles, unpin/re-pin Default pin should result in a profile specific pin).
 

Comment 1 by gab@chromium.org, Mar 9 2016

Note: the desktop shortcuts created do work properly. The issue is with manually pinned entries.

The windows are supposed to have properties that tell Windows what to encode in the pin, seems to be broken (maybe Win10 only).
Cc: pbomm...@chromium.org
Labels: Needs-Bisect
Cc: ashej...@chromium.org
Labels: Needs-Feedback
I am unable to reproduce the above issue on Windows 10 with chrome version '50.0.2661.11' & canary version '51.0.2673.0'. Please find the attach screen below.

@gab: Please check the same and let me know if I missed something.

Appreciate your help.

Thank you!
593414.mp4
2.9 MB Download

Comment 4 by fdoray@chromium.org, Mar 18 2016

Cc: fdoray@chromium.org
Labels: -Needs-Bisect
@gab: Friendly Ping! Would you mind checking the above issue as per comment#3 ? Removing the bisect label for now. Do add if required.

Also, if it's not much to ask can you please try the above issue on latest chrome versions ?

I really appreciate your help.

Thank you!

Project Member

Comment 6 by sheriffbot@chromium.org, Dec 19 2016

Cc: ew...@chromium.org bzanotti@chromium.org msarda@chromium.org
Status: Available (was: Untriaged)
--Chrome Identity automated triaging--

This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -bzanotti@chromium.org
Cc: -ashej...@chromium.org
Project Member

Comment 9 by sheriffbot@chromium.org, Nov 1

--Chrome Identity automated triaging--

This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 30

Cc: droger@chromium.org jlebel@chromium.org tangltom@chromium.org sabineb@chromium.org bsazonov@chromium.org
Status: Archived (was: Available)
--Chrome Identity automated triaging--

This available, signin or profiles-related bug has gone at least 30 days since the last automated post without any further update. This bug will be closed out due to inactivity. Please re-open the bug and provide an update if it is still a valid or reproducible bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Untriaged (was: Archived)
This is still a problem, same as described in OP
Cc: -droger@chromium.org -ew...@chromium.org -bsazonov@chromium.org -sabineb@chromium.org -tangltom@chromium.org -jlebel@chromium.org brucedaw...@chromium.org
CC+ brucedawson

I think this is a Windows specific issue. I think it would be better if a person that works on Chrome Windows takes a look at it.
Project Member

Comment 13 by sheriffbot@chromium.org, Jan 4

Status: Available (was: Untriaged)
--Chrome Identity automated triaging--

This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: davidbienvenu@chromium.org
Status: Assigned (was: Available)
I can look at this while I'm looking at crbug.com/328738
When I create a new profile, the only thing I can do from the taskbar icon context menu is close the window; I can't pin it. If I  shutdown Chrome and then open Chrome with the new profile, I can pin that taskbar icon successfully. This is Windows 10, shipping version of Chrome (M71). The new profile is the 4th, not the second, but I'd be surprised if that matters.
Cc: -fdoray@chromium.org
(not my area of expertise)

Sign in to add a comment