I can see a modest excuse for restricting the sidebar view to Bing, in that you need to have a reasonably suitable display format for the results.
Microsoft can be aware of and support the case from both sides, but I could imagine Google detecting "User-agent = Edge and the window width=300px", and sending some experience-ruining CSS or JavaScript to try to nudge users back to Chrome.
I know there was a while where various Google properties were unreasonably clunky on Firefox, and I can't imagine it was by accident; doubtless a trillion-dollar company can wire up a few CI instances to make sure things load well on non-Chrome browsers.
I agree and did try messing with the views a bit vs. bing.com and realized it's not the same. Fair enough!
But to introduce a sidebar in a chrome-based browser just to ship Bing? and then add it to every right click context for only Bing, overriding your other search preferences? and the sidebar just redirects you to open the search in a new tab/window anyway (was at the bottom of the screen for me)?
Microsoft can be aware of and support the case from both sides, but I could imagine Google detecting "User-agent = Edge and the window width=300px", and sending some experience-ruining CSS or JavaScript to try to nudge users back to Chrome.
I know there was a while where various Google properties were unreasonably clunky on Firefox, and I can't imagine it was by accident; doubtless a trillion-dollar company can wire up a few CI instances to make sure things load well on non-Chrome browsers.