Jul 05 2019 11:54 PM
Latest Edge Canary 77.0.211.0 has added a couple issues:
Anybody else having these issues? Any workaround?
Jul 08 2019 11:06 AM
SolutionJul 08 2019 02:37 PM - edited Jul 08 2019 02:40 PM
To All,
I swear, I recall someone saying, it's known & will be fixed asap ;) Yet, there is a caveat from this, a lesson to be learned.... don't run Canary, exclusively. Use Dev and have Canary out of interest, curiosity & the exercise of looking for/at daily changes before they hit Dev. Run with Dev & (sure) have Canary, as well, not, as your primary Edge C! "Use Dev, investigate Canary". In other words, don't be relying on Canary.
Cheers,
Drew
Jul 08 2019 02:50 PM
@Drew1903
I use this as my main browser now, just so devs get more "Production" telemetry, and if something crashes really hard, like unusable, I can always get back to "classic" Edge, or Firefox or other fallbacks. The only event that would really prevent me from helping improve the product would be a security/privacy disaster - if the data collected were exposed, well, that would be a hit I'd not forget. Usability problems - meh, I guess most of Windows users got used to this ;)
Jul 08 2019 05:44 PM
@Rohit Yadav - thanks - just manually checked for update and it's resolved!
Jul 09 2019 08:25 AM
Jul 12 2019 08:18 AM
Same here, with edge dev.
Jul 12 2019 12:09 PM
@jantjec1
This has been fixed in Canary. Yours is the 1st mention I have seen of it happening with Dev. I cannot repro the behavior in Dev you describe; it keeps working properly, exclusively.
Cheers,
Drew
Jul 13 2019 12:20 AM
Check for any available updates @jantjec1 ...
Jul 13 2019 03:53 AM
Reinstalled Dev and now it's ok.@Drew1903
Jul 13 2019 11:57 AM - edited Jul 13 2019 12:00 PM
@jantjec1
Cool, good to hear :thumbs_up::thumbs_up:
Cheers,
Drew
PS: btw, my name is, actually, Drew. @ Drew 1903 is a User Name.
Jul 19 2019 05:23 PM - edited Jul 19 2019 05:31 PM
@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.
Jul 19 2019 05:30 PM
@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