Nov 21 2019 02:07 PM - edited Mar 18 2020 10:56 AM
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
Nov 23 2019 02:01 AM
Nov 25 2019 11:46 AM
Nov 25 2019 12:33 PM
Nov 27 2019 03:09 PM
Thanks for the clarification
For the immersive reader, nothing is planned in the registry or policy to disable it (Chrome always this option) ?
And in flags, we can disable reading aloud, but not the reader, it's weird
For the 3rd (about: blank) I have the start page of my ISP
But I have this problem too when I click on a shortcut. But no problem if Edge is already open.
It looks like Edge is slowed down when I open the web page and it has appeared since some versions and Canary
Thanks
Nov 27 2019 09:05 PM
Dec 02 2019 12:14 PM
Always points 2, 3 and 4 with the latest version of CanaryCa would be nice if it could be "quickly" corrected, it's a little painful
Dec 02 2019 01:08 PM
Dec 02 2019 01:16 PM
The icon in the address bar
Having the choice to have it or not would be better
And I find this 351 less fast (less fluid)
Dec 02 2019 01:20 PM
Dec 02 2019 01:26 PM
Dec 16 2019 10:20 AM
Always the problems and "bugs" with the latest version of Canary (81.0.366)
I do not know if the MS staff saw these requests and if they intend to resolve them or not
Dec 16 2019 12:42 PM
@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 Edge
Dec 16 2019 01:10 PM
@Deleted
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
Dec 16 2019 01:35 PM
@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!
Dec 16 2019 01:40 PM
@Deleted
Thanks for your help
I like this browser and only use this one
Dec 20 2019 02:32 PM - edited Dec 20 2019 02:35 PM
@Deleted
Hi
I tested the latest version of Edge Beta (79.0.309.54), same problem for the #4 (text frames) but it's ok for the #3 (about:blank)
If it can help you
Dec 24 2019 04:35 AM
@Deleted
For #2 (immersive reader), there was that before in edge://flags
If these options can be re put
Thanks
Dec 24 2019 10:00 AM
@tistou I'm glad to hear that the about:blank page has resolved! The flag for immersive reader disappearing is by design, we usually remove a flag once the feature is stable enough to be turned on for good. Can you tell us more about how having it again would be helpful?
And the devs wanted to know if you had tried #4 in Chrome Canary? (Their Stable runs several months behind, so it's not always as helpful with diagnostic testing.)
Thanks,
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
Apr 14 2020 12:54 PM - edited Apr 14 2020 12:56 PM
SolutionWith 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.