Forum Discussion
Solved
Some bugs and suggestions with the latest versions (Canary)
Hello
1 - Since the .340 version, when I click on the button Restart (changes of an option in edge://flags/)the browser closes but does not reopen (the Edge process is still running in the task manager)
2 - Possible to re-put the option to disable the immersive reader (as it was before) in edge://flags/ (or in edge://policy/ )
Easy to set up and everyone is happy 
3 - If "Browsing history" in edge://settings/clearBrowsingDataOnClose is enable, it causes the bug to have about:blank page when we open Edge before having the requested web page (shortcut, start page, clickable link, etc ...)
If the browser is already open, and I open a web page from a shortcut, clickable link from software, etc... I have the requested page directly in new tab (no about:blank)
4 - Always display bugs in text frames or clickable buttons of some sites
Thanks for your great work
With regards to the black bar on focusable elements this change is by design and was tested with end users. From an aesthetics perspective the change was roughly a 50/50 split for/against but it was more preferred by users that have a need for higher contrast colors. Because of our focus on accessibility we decided that it broke the tie. We go over this change in our blog post about the updated form controls. This change has landed in Chromium itself and will be visible in Chrome started in version 83.
And Firefox is also considering aligning with our adjustment too due to the accessibility benefits.
Thanks as always for the feedback and please keep it coming.
tistou Thanks for bringing those points with Canary to our attention! We'd love to get a better understanding of them, so it would be great if you can answer the following:
2 - Can you tell us more about when and how it would be helpful to have immersive reader disabled?
3 & 4 - Hmmm, interesting. Do you have access to Chrome Canary, and if so, do you encounter the same issues with about: blank and the lack of a "text" cursor?
And thank you, HotCakeX, for your troubleshooting assistance on this thread and the other.
Fawkes (they/them)
Project & Community Manager - Microsoft EdgeDeleted
Thanks so much for your interest in this topic
2) I asked if it was possible to re-put the option in edge://flags to disable the immersive reader (as it was before)
There is always the option to disable the grammar of the immersive reader, but not the reader
3) No problem with Google Chrome (and no problem with Edge Chromium 79.0.309 that I recently re-tested)
4) No problem with Google Chrome (and no problem with the old version of Canary, before the .300 if I remember correctly)
Thanks so much
tistou Thanks for your fast response. That's all good to know and I'll loop back with MissyQ, josh_bodner, and the rest of the team to dig deeper into this.
Please let us know if you notice anything else similar!
- Hi,
I've experiencing the first issue too (I thought it was only my system acting up).
enabled some flags but had to manually reopen the browser.
Windows 10 insider
Version 80.0.341.0 (Official build) canary (64-bit)- Good,
about the 2nd one, it's not an issue, Microsoft finally decided to roll out immersive reader mode to everyone by default, just like in Edge classic.
features only stay in flags temporarily, after the tests are done and they are ready, Microsoft adds them by default to the browser.
3rd,
on startup settings edge://settings/onStartup , which one is selected?
4th, I'm also seeing it on latest canary.
