Forum Discussion
Edge Canary 77.0.211.0 always on top, dropdown menus not functioning
Latest Edge Canary 77.0.211.0 has added a couple issues:
- Edge is always on top. Unless I minimize the edge window(s) , no other program or app can be brought to the foreground, except for other Edge windows.
- html dropdown menus don't work. I can click on them but the menu does not popup, only the field gets selected. Navigation up and down the menu is possible by using the up and down arrows.
Anybody else having these issues? Any workaround?
- It is fixed now. Thanks for the response...🙂
71 Replies
I hate always on top it's confuse me!!!!!
- always on top problem was in Google Chrome Canary too but few days ago it got patched. now Microsoft should patch it as well. it's related to the chromium engine.
- I have the same problem. I'm not sure when did the problem show up, but it is still unresolved. I'm now at "Version 77.0.211.0 (Official build) canary (64-bit)" and my system is 1809,17763.557. It is annoying because I often use edge to preview my web page ,so I need to switch from edge to the editor frequently. This problem lets my efficiency drop,and reinstall the browser doesn't work at all.
- Why Edge set SetWindowPos to HWND_TOPMOST in the first place, makes no sense to me.
It _could_ be a feature like in many applications, where it is a user option.
I am experiencing the exact same issues on my 77.0.211.0 build.
Why Edge seems to be set to set SetWindowPos HWND_TOPMOST makes no sense to me.
- Same issues here.
(Windows 10 - 1809) Thank you all, we are aware of this issue. We will get this issue fixed as soon as possible. Until then, the Developer channel does not have this issue.
Came here to see if there was a post about this. I've had to go back to Chrome for now because Edge won't let any other window appear over it. Windows 10 1903 and Edge Canary version 77.0.211.0. Hope it gets fixed soon.
Or, Sean, you could just use Dev, instead. It works fine & doesn't stay on top. Dev is, always, more stable or in this case, less weird than Canary may be on occasion (more often).
Suggestion: Treat Dev as 'primary' & Canary as secondary... I mean, poke about at Canary, but, treat Dev as the one being used. Canary is interesting; with its daily changes... Dev is better/best for steady use. I have both, but, made Dev the default browser not, Canary.
Cheers,
DrewDrew1903 Like I said I'm fine with Canary. I very rarely have a issue with it. I've had two issues since its release. Both fixed in less than two days. Besides it takes <30 seconds for me to switch my default browser when a bug like this occurs. So I'll stick with Canary till release. I like testing the latest updates, and fully understand the risk in terms of stability. Just like I fully understand to expect issues when I occasionally hop onto the Window 10 Insiders ring. But as I said Edge has been surprisingly solid even with me using the Canary branch.
MarcoMangiante Oh I know. I don't mind going back and forth. I completely understand issues like this are going to happen when using the canary channel of a browser that isn't even in a beta release status yet :P mainly just came to make sure it wasn't just me experiencing this.
