08-12-2019 12:57 PM - edited 08-13-2019 05:15 AM
08-12-2019 12:57 PM - edited 08-13-2019 05:15 AM
Although I chose Google, Edge is using Bing to do web searches.
*Version 18.104.22.168 (Official build) canary (64-bit)
08-12-2019 01:15 PM
08-12-2019 01:15 PM - edited 08-12-2019 01:17 PM
08-12-2019 01:16 PM - edited 08-12-2019 01:19 PM
08-12-2019 01:20 PM
08-12-2019 01:39 PM
I do not use google. However, I tried to repro your issue & cannot. Changed to google, address bar searches immediately > Google. Change back to Bing, they immediately > Bing.
08-12-2019 02:33 PM - edited 08-12-2019 02:39 PM
@Wouldiwas_Shookspeared I just got this issue as well with 22.214.171.124. As soon as I told Edge to restart to finish updating it started happening. I've tried removing all search engines, going back to google doing a search there so it shows up as a option in Edge again and it still uses bing when I use the address bar to search. Not a huge deal, I know to expect problems since I'm on the canary branch. Just wanted to make sure it wasn't just me.
Edit: Going into settings and adding Google search manually using this url
Gets it working again for me, so I'll just use that workaround for now.
08-12-2019 03:55 PM - edited 08-12-2019 04:00 PM
Ooops, I should read more slowly. I think I had checked this in Dev not, Canary. Yes, in Canary when set to google it 'says' or looks like it's going to use google, but, does, still, use Bing. Good I prefer Bing, anyway. Obviously, it is something the Team needs to correct. I have submitted this to Mr. Smiley & urge others to follow suit.
08-13-2019 05:13 AM
It was my fault. I should have mentioned the version I am using. I will correct this information in the original post, and I will always take care to mention this in future posts. Thank you
08-13-2019 06:55 AM
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).
08-13-2019 10:19 AM
08-13-2019 11:21 AM - edited 08-13-2019 11:21 AM
(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.
08-13-2019 11:36 AM
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). :)
08-13-2019 11:48 AM - edited 08-13-2019 01:22 PM
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.
08-13-2019 11:50 AM
Why is that surprising? As far as I can tell, this bug is only days old (is for me anyway).
08-13-2019 11:55 AM - edited 08-13-2019 11:56 AM
Maybe, it's me, then that has or had it backwards & it will surface in Dev with the next Dev update, if they don't fix it first, of course. Either way, good we find & report things.
08-13-2019 12:10 PM
08-13-2019 01:11 PMSolution
08-13-2019 01:26 PM
Yea, it's fixed and now I see that this is just a favicon, as I had to use it once for it to change.
08-14-2019 06:08 AM - edited 08-14-2019 06:13 AM
If someone deleted Google Search Engine (like me), just add a new engine with these parameters:
The above huge URL is the "official" one (I suppose ), but these two also work:
@Wouldiwas_Shookspeared I have the same issue on Chromium Edge for both Mac and Windows, even when you go to the search bar and type google - tab - fill in search query, it refers to Bing. Despite that I have removed every single Search engine but Google, it keeps on going back to bing.
I've tried to use your base-url, but Chromium Edge does not seem to like the word google anymore, it even automatically replaces it with bing.com
The latest canary version of Edge (Version 126.96.36.199 (Official build) Canary(64-bit))
@HotCakeX You would assume that they are both on Mac and Windows launched at the same time, but I guess that is not the case here right now as there are no updates for any of my Microsoft products available atm.