Forum Discussion
Dev channel update to 81.0.381.0 is live
This problem doesn't exist on Edge insider canary Version 81.0.389.0 (Official build) canary (64-bit)
so whatever bug it was, they fixed it already, just need to wait it out until the next Dev update 🙂
HotCakeX Incorrect—this taskbar icon bug confidently reproduces on Microsoft Edge Canary 81.0.389.0.
I reproduced it under 15 seconds...bolding your text that "this bug really doesn't exist on Canary" doesn't make it any more accurate, for what it's worth.
https://streamable.com/rd49b (HotCakeX's "test" from yesterday's Canary build)
Please read the reproduction steps more carefully, before making unfortunately erroneous claims. The bug doesn't affect every site. I've tested on two Edge Canary systems now with identical behavior. A screenshot from the system: the left is Canary; the right is a site-app pinned to the taskbar, from Canary. Renders the entire pinning icon system useless. Still needs to be fixed.
Canary is as broken as Dev on this bug. Canary might even be worse because now that icon sometimes will take you to the new tab page. Either you did not test enough sites or mistakenly used a PWA or an already-cached icon or you hit another corner-case.
ikjadoon
Pinned icons changing from specific to Edge when pinned to taskbar affects sites converted to apps. It does not apply to sites Pinned to taskbar via More tools & NOT converted to apps. I have just tested ALL 3 current Channels (again) and can confirm the bug, the behavior IS, still, happening in all 3. You are correct.
Cheers,
Drew- Look at my videos above.
p.s no conversion happens. Edge can't convert sites into apps.
- Spoiler
ikjadoon wrote:HotCakeX Incorrect—this taskbar icon bug confidently reproduces on Microsoft Edge Canary 81.0.389.0.
I reproduced it under 15 seconds...bolding your text that "this bug really doesn't exist on Canary" doesn't make it any more accurate, for what it's worth.
Bug reproduced on Canary 81.0.389.0 (HotCakeX's "test" from yesterday's Canary build)
Please read the reproduction steps more carefully, before making unfortunately erroneous claims. The bug doesn't affect every site. I've tested on two Edge Canary systems now with identical behavior. A screenshot from the system: the left is Canary; the right is a site-app pinned to the taskbar, from Canary. Renders the entire pinning icon system useless. Still needs to be fixed.
Canary is as broken as Dev on this bug. Canary might even be worse because now that icon sometimes will take you to the new tab page. Either you did not test enough sites or mistakenly used a PWA or an already-cached icon or you hit another corner-case.
- It wasn't happening on Canary.
- it wasn't a claim, it was a fact and what I experienced.
- I read your reproduction steps carefully enough, still wasn't happening.
- it's still not happening, Version 81.0.392.0 (Official build) canary (64-bit)
- I tested on the site you mentioned, Twitter.
A bug does not need to hit 100% of the users to be a bug. I appreciate the follow-up troubleshooting here.
1. It was written that "it's not happening in Canary" when it can be reproduced on Canary. It's more precise (and helpful) to say, "Not happening on my Canary build with these steps."
2. It was claimed that dev users they just "need to wait", as the bug was "fixed" in Canary. That's not accurate.
3. True: as I wrote in that same first post, the taskbar icons can be cached.
4. ...again, if it's been cached, then the bug doesn't reproduce.
5. ...again, it could be cached or it could be Twitter's PWA (Twitter logged out doesn't present as a PWA on Dev; on Canary, even the logged-out state is recognized as a PWA).
Canary 81.0.392.0 is, by far, even buggier in installing apps. Some of the time, Edge Canary 81.0.392.0 won't even create the app (i.e., the menu button does nothing), takes ~20 to 30 seconds to create the app, and/or doesn't even use the favicon correctly after installing (not even pinned and it's got the wrong icon).
This bug is best reproduced on sites you've never tried to install as an app before, non-PWAs, pinning immediately after creation as an "app", and: those might not be all the conditions, but they are some. Even I can make the Google.com favicon cache on my Dev build (81.0.381.0), if I either let the window stay open for a long enough time before attempting to pin or keep uninstalling/reinstalling the site:
This bug does have corner cases where it works and where it doesn't work. But, the bug exists (on all 3x systems I own on Dev 81.0.381 + 2x systems on Canary 81.0.392.0 + 1x systems on Canary 81.0.389.0). The Canary builds are only on two of the systems and I only could test one with yesterday's Canary build, as the other had already updated.
I also created new profiles on each and the bug remains. Because of the unusual retention of whatever icon Edge wants (the correct favicon or the wrong default), as I stated in my initial post, it looks like a caching problem.
//
Again, yes: this is not a bug with "Pin site to taskbar", which simply creates a browser shortcut. "Installing" a site as an app removes the browser UI ("chrome") & forces it to always launch in a new window.
- Spoiler
ikjadoon wrote:A bug does not need to hit 100% of the users to be a bug. I appreciate the follow-up troubleshooting here.
1. It was written that "it's not happening in Canary" when it can be reproduced on Canary. It's more precise (and helpful) to say, "Not happening on my Canary build with these steps."
2. It was claimed that dev users they just "need to wait", as the bug was "fixed" in Canary. That's not accurate.
3. True: as I wrote in that same first post, the taskbar icons can be cached.
4. ...again, if it's been cached, then the bug doesn't reproduce.
5. ...again, it could be cached or it could be Twitter's PWA (Twitter logged out doesn't present as a PWA on Dev; on Canary, even the logged-out state is recognized as a PWA).
Canary 81.0.392.0 is, by far, even buggier in installing apps. Some of the time, Edge Canary 81.0.392.0 won't even create the app (i.e., the menu button does nothing), takes ~20 to 30 seconds to create the app, and/or doesn't even use the favicon correctly after installing (not even pinned and it's got the wrong icon).
This bug is best reproduced on sites you've never tried to install as an app before, non-PWAs, pinning immediately after creation as an "app", and: those might not be all the conditions, but they are some. Even I can make the Google.com favicon cache on my Dev build (81.0.381.0), if I either let the window stay open for a long enough time before attempting to pin or keep uninstalling/reinstalling the site:
This bug does have corner cases where it works and where it doesn't work. But, the bug exists (on all 3x systems I own on Dev 81.0.381 + 2x systems on Canary 81.0.392.0 + 1x systems on Canary 81.0.389.0). The Canary builds are only on two of the systems and I only could test one with yesterday's Canary build, as the other had already updated.
I also created new profiles on each and the bug remains. Because of the unusual retention of whatever icon Edge wants (the correct favicon or the wrong default), as I stated in my initial post, it looks like a caching problem.
//
Again, yes: this is not a bug with "Pin site to taskbar", which simply creates a browser shortcut. "Installing" a site as an app removes the browser UI ("chrome") & forces it to always launch in a new window.
The bug is best reproduced on a fresh Windows 10 installation and that's exactly what i did by doing the test on Edge dev and it wasn't happening as you could see.
on a fresh Windows 10 installation, where no user modification has applied, it doesn't matter whether 100% users experience it or not, it won't be relevant anymore, because we eliminate the unique user configurations factor entirely.
ikjadoon Here's another broken build:
https://streamable.com/4ei7r
Before people want to ask "Why?" or "Not supported", this exact behavior is explicitly recommended by Edge:
Corner cases exist. Not all users get all bugs. But, let's not dismiss bugs without thoroughly testing them. Now we've properly added the latest two Canary builds to the "failing" category.
This is unbelievable lol
I just tested Dev channel on a brand new Windows 10 installation (Windows Sandbox)
Version 81.0.381.0 (Official build) dev (64-bit)
here is the result:
- Spoiler
ikjadoon wrote:ikjadoon Here's another broken build:
Video reproducing the bug in 20 seconds on today's Canary 81.0.392.0 build
Before people want to ask "Why?" or "Not supported", this exact behavior is explicitly recommended by Edge:
Corner cases exist. Not all users get all bugs. But, let's not dismiss bugs without thoroughly testing them. Now we've properly added the latest two Canary builds to the "failing" category.
Here, watch it
proof that Edge Version 81.0.392.0 (Official build) canary (64-bit) is Not broken.
my suggestion: try fully uninstalling your Edge and reinstall it again.
- Another video, because on the first one I accidentally closed Edge's main window before pinning Google to taskbar so you might say I cheated or something, here is the exact steps you showed in your own video
https://streamable.com/8m9so
so what am i missing?
