No indication to the user when pinning to the taskbar in welcome screens fails
Categories
(Firefox :: Messaging System, defect, P2)
Tracking
()
People
(Reporter: michaelahughesuk, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
At the moment, developer / beta builds of Windows block applications from pinning to the taskbar using older mechanisms for pinning. There is a newer API that can be used, but even when it is used, Windows still sometimes blocks pinning. There is currently no indication to the user that pinning was blocked.
To test, use a latest developer version of Windows (through the Windows Insider program), have Firefox installed and not pinned, do the onboarding / welcome flow (about:welcome) and ensure that pinning is checked before hitting save and continue.
If it still pins, try doing this many times in a row. It will eventually trigger windows blocking it and the user will not be notified.
In practice with the newer APIs in use, Windows still randomly seems to block pinning (without having done it many times already). I don't know what circumstances cause the block and they are not documented anywhere. With the newer API, there is a system notification confirming the user wants to pin first, and possibly Windows blocks it if they think the user has seen too many notifications.
Comment 1•7 months ago
|
||
Thanks for filing - I'm removing priority to make this go into our triage queue.
Comment 2•7 months ago
|
||
NI UX and product for feedback on potential direction of error handling on about:welcome screens
We should figure out a follow up to let users know what esle needs to be done. I will open a jira ticket for UX
Description
•