Sep 14 2021 12:23 PM
On Microsoft Edge Dev 95.0.1000.0, type search terms into the address bar and hit enter. Nothing happens. I also noticed that highlighting text and right-clicking no longer has the option to search for the highlighted text. If I perform the same procedure on Microsoft Edge Stable 93.0.961.38, it searches Google with the entered/selected terms, as expected.
I noticed that the default search engine in Edge Settings appears to be corrupt in Edge Dev and looks okay in Edge Prod.
In our company, the default search engine is managed by a GPO, per the instructions / example in the GPMC. This registry entry is shared between all versions of Edge on a machine…so it seems as though Edge Dev has the issue if Edge Stable still works fine.:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"DefaultSearchProviderEnabled"=dword:00000001
"DefaultSearchProviderSearchURL"="{google:baseURL}search?q={searchTerms}&{google:RLZ}{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchFieldtrialParameter}{google:searchClient}{google:sourceId}ie={inputEncoding}"
I am virtually certain that this is a Microsoft Edge Chromium bug... I’m pretty sure it started with Edge Dev 95.0.1000.0, but I cannot say for sure.
Thoughts?
Sep 21 2021 02:28 PM
@Metroparks Thanks for reaching out and thanks for the detailed report! It looks like the team has received other similar feedback reports. They are currently investigating and we'll let you know if they have any updates or if they have any follow up questions.
-Kelly
Sep 21 2021 09:31 PM
@Kelly_Y, I am happy to let you know that I just got the update to Edge Dev 95.0.1020.0 (Official build) dev (64-bit), and this issue seems to be fixed in this build!! Thank you!!
Sep 22 2021 10:16 AM
Sep 22 2021 03:47 PM
Sep 24 2021 02:46 PM
@Deleted Hi! The issue should be fixed in v94. We are expecting a Stable release today. Please test and let us know if you are still reproducing after updating. Thanks!
-Kelly
Sep 27 2021 08:07 AM
@Kelly_Y Thanks for the quick feedback, and having validated that the fix had been backported! I do confirm that the issue seems solved in build 94.0.992.31.