Is there something special about 28.16.0 that might have contributed to this new incompatibility? Or do you think Microsoft made some Chredge/Chrome-centric change to Bing that would account for it? I've done around 1000 Bing reverse image searches in Pale Moon over the past four months and this is the first time I've run into a problem.
Additional Intervening Changes:
- I completely disabled uBlock Origin and eMatrix for Bing.
- The only Pale Moon extension changes I wittingly made were upgrading from Splashed 1.2 to 1.3, switching from DownThemAll 3.0.8 to DownThemAll *nightly* 3.0.9pre.2019.08.20.00h00m09s, and installing GitHub Web Components Polyfill 1.1.6.
- I disabled "Modern Standby" (fka "Connected Standby") in my Windows registry in order to disable wake-on-mouse and wake-on-keyboard, but I'm not seeing how that would have any impact on this issue.
Google reverse image search generally wins on sheer volume of hits returned, but Bing reverse image search generally wins on everything else. Bing's filtering tools, presentation options, and dimension information are markedly more useful than Google's. Bottom Line: I can usually identify an image and find a "better" copy of it more quickly using Bing than I can using Google.