3 ms·
Here is a nafarious interpretation of events: (I assume we all remember how Alphabet, in order to drive Chrome adoption, sabotaged youtube when a Firefox-browse
by alcoholic_byte 3y ago
Here is a nafarious interpretation of events:
(I assume we all remember how Alphabet, in order to drive Chrome adoption, sabotaged youtube when a Firefox-browser was detected?)
Only breaking for new FF-versions will give the untechnical user the impression that FF broke through an upgrade.
So I call this another not so feeble, but very evil(yes I think we expect nothing less of them right now), attempt of Google go tighten the grip on the Browser-eco-system.
Not the least that it only impacts FF on Android.
On Android the means to inspect are limited without a computer(so they might hope for users to switch because they need access and then forget to switch back).
That is also, to me, a sign that it was intentional, just because how specific, browser-centric this is.
- 6510 3y agohere is a fun anecdotal: google wouldn't load for me on ff windos, I tried a bunch of stuff over a few days then in a lapse of sanity or a stroke of genius I decided to switch the default search engine [back] from bing to google, I press reload and the html page with the single form field worked again! It continued to work after switching to bing again. I feel I should note I have this in a user script: document.getElementsByClassName('b_logoArea')[0].href = "https://google.com/search?"+document.URL.match(/q\=[^&]*/); It makes it so that clicking the bing logo sends the query to google, perhaps it doesn't like getting queried directly without being the default search engine?