Forum Discussion
Edge Canary 77.0.211.0 always on top, dropdown menus not functioning
- Jul 08, 2019It is fixed now. Thanks for the response...🙂
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.
- Drew1903Jul 07, 2019Silver Contributor
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,
Drew- sean8102Jul 20, 2019Brass Contributor
Drew1903 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.
- Drew1903Jul 20, 2019Silver Contributor
sean8102
Sean, I have been running both Dev & Canary. I have to agree with you, overall, considering just early betas, they do, both, seem (surprisingly) solid. That's rather impressive & a compliment to the Team. The hiccups fairly minor & as you say rectified promptly. Cool too the responsiveness of the Team to Feedback.
Cheers,
Drew
- MarcoMangianteJul 07, 2019Iron Contributor
- sean8102Jul 07, 2019Brass Contributor
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.