[meta] Implement Web App Manifest support for taskbar tabs
Categories
(Firefox :: Web Apps, task, P3)
Tracking
()
People
(Reporter: ericchen647, Unassigned)
References
Details
(Keywords: meta)
Attachments
(1 obsolete file)
If available, we will use the PWA manifest to obtain web app start URL, name, scope and icons
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•10 months ago
|
Updated•9 months ago
|
Comment 3•2 months ago
|
||
Unassigning myself since manifest icons are finally supported. This bug can be re-used for other missing manifest features (of which there's plenty, we only deal with the tiniest subset at this point).
I celebrate this step forward, but the aliasing of the icons is certainly two steps back. The first two here are Firefox; the last one is another browser with much softer edges. Really off-putting.
In Taskbar Tabs, icons are the absolute protagonists, so I really encourage you to take a minute to revise this.
Comment 5•2 months ago
|
||
(In reply to Ugi from comment #4)
I celebrate this step forward, but the aliasing of the icons is certainly two steps back. The first two here are Firefox; the last one is another browser with much softer edges. Really off-putting.
Hmm, can't reproduce on my end but I agree the jaggedness you're seeing isn't great. Can you file a new bug for this?
(While you're filing the bug, to avoid me needing to make a Spotify/WhatsApp account, can you also use the DevTools' "Application" panel on the sites and add the link to the manifest listed? In my case I'm getting https://open.spotifycdn.com/cdn/generated/manifest-web-player.1609946b.json, but I'm not logged in. If you have trouble just file the bug without.)
(In reply to Duncan McIntosh [:dmcintosh] from comment #5)
(In reply to Ugi from comment #4)
I celebrate this step forward, but the aliasing of the icons is certainly two steps back. The first two here are Firefox; the last one is another browser with much softer edges. Really off-putting.
Hmm, can't reproduce on my end but I agree the jaggedness you're seeing isn't great. Can you file a new bug for this?
(While you're filing the bug, to avoid me needing to make a Spotify/WhatsApp account, can you also use the DevTools' "Application" panel on the sites and add the link to the manifest listed? In my case I'm getting https://open.spotifycdn.com/cdn/generated/manifest-web-player.1609946b.json, but I'm not logged in. If you have trouble just file the bug without.)
I'm actually the author of 1985410. I mentioned the jagginess there and uploaded a link to an image of the pinned notification request with a pretty aliased icon too. It already has some traction, and it's still open, so I don't think creating a new bug would help.
Regarding the manifest, I also get https://open.spotifycdn.com/cdn/generated/manifest-web-player.1609946b.json when I'm logged in, so it seems to be the same for both.
WhatsApp returns https://web.whatsapp.com/data/manifest.json.
Description
•