mark taskbar pinning methods as unsupported in msix builds
Categories
(Firefox :: Shell Integration, enhancement, P3)
Tracking
()
People
(Reporter: agashlin, Assigned: bhearsum)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidedi-tikka])
Attachments
(1 file)
nsWindowsShellService.isCurrentAppPinnedToTaskbarAsync() currently relies on matching paths in the shortcut. This does not work for a packaged app. The UWP API TaskbarManager.IsCurrentAppPinnedAsync is the way to handle this for a packaged app.
I have a rough WIP, from trying to get RequestPinCurrentAppAsync working. It would need to be in addition to the existing implementation since this is only available from within a package.
This would only really be of use for telemetry. Aside: os.environment.launch_method is always Other when launching a package, whether it was opened from a taskbar pin, start menu shortcut, or desktop shortcut; there must be some amount of indirection so that we don't know the shortcut that opened us.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
bugherder |
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 4•2 years ago
|
||
Re-opening because the landed patch is just preventing us from lying about supporting pinning in MSIX - not actually implementing it.
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
(In reply to bhearsum@mozilla.com (:bhearsum) from comment #4)
Re-opening because the landed patch is just preventing us from lying about supporting pinning in MSIX - not actually implementing it.
I was reminded recently that we are strongly discouraged from adding additional patches onto fixed bugs because it messes up tracking flags and various queries. For that reason, I re-filed this as https://bugzilla.mozilla.org/show_bug.cgi?id=1794159 for the actual implementation.
Description
•