Forum Discussion
Look at your Search Engine settings... are you using the new 'Google-Bing' search engine? lol
- Problem Fixed:
Version 78.0.246.0 (Official build) canary (64-bit)
update your Edges 😉
Deleted
Same issue. Canary. Selecting Google (Default) searches Bing, even though my entry looks correct, but look at the icon next to Google (it's Bing's icon):
Manually adding does work for me as well (even seems to fix the "bad" Google entry).
Keith Davis
(Suggest) There is something worth noticing here. There are 3 beta channels (well, there will be 3 soon). Canary is the most like to have issues. And here we have a problem in Canary which, does not exist in Dev. It's this kind of scenario where running more than one track can be interesting. Sure should be reported as needing to be corrected in Canary, even though, it, already, does not need to be corrected in Dev.
Cheers,
Drew
I understand. My users (actually just one right now) are running Dev, but as a Dev myself and responsible for the deployment of this, I tend to always run the bleeding Edge (pun intended). As far as not being needed to be corrected in Dev, that is assuming that it is fixed before the code is merged into the Dev branch. The Edge team seems to be doing this well, but if this made it to Dev, would not be the first time that Microsoft did not listen to insiders and bugs made it to the final release (aka, 1809 issues). 🙂
Keith Davis
I may not have worded what I'd written very well. The issue is in Canary, but, NOT in Dev. Meaning, it seemed interesting that was ok in Dev yet messed up back in Canary. In other words, in regard to your point, no bug seems to be 'carrying over' because, Dev does not have the issue. Or, it's a wee bit surprising finding something ok in Dev whilst awry back in Canary. I trust this is written more clearly than before.
And, I can certainly appreciate (1st hand), there are reasons why we IT Pros & Developers are drawn to particular beta levels; or more than one track.
Cheers,
DrewWhy is that surprising? As far as I can tell, this bug is only days old (is for me anyway).
