Earlier quoted context omitted.
It actually insert a line break on enter, make it invisible and can't be deleted only on firefox. Pretend firefox as chrome makes it works perfectly. They lock the community thread and fixed that after several days I found the finding and post it there. Shame on you, google.
Oh my god. I knew it was inserting a line break when I hit enter but I didn't realize it was a FF only issue. gdi Google.
Chrome phasing out support for User-Agent
121–130 of 329 posts
Re: Chrome phasing out support for User-Agent
#122The weird thing about this is that the only company I've seen doing problematic user-agent handling in recent years is Google themselves. They have released several products as Chrome-only, which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent. Same with their search pages, which on mobile were very bad in every non-Chrome browser purely based on user age…
Every single Google product is slower on Firefox and it’s hard to not call this malice and artificial. Many people check out Gmail and GMaps on Firefox and go back to Chrome because of their clunkiness on Firefox.
are you actually asserting that Google is purposefully adding code/"tweaking" their web apps to run slowly on browsers other than Chrome?
do you have any evidence at all for this other than anecdotes about people experiencing Google web app clunkiness on Firefox?
Re: Chrome phasing out support for User-Agent
#123Ah, the end of the countless references to KHTML :) As a long time KDE user I'm a little sad, but also fully aware this day would come.
Re: Chrome phasing out support for User-Agent
#124Earlier quoted context omitted.
It actually insert a line break on enter, make it invisible and can't be deleted only on firefox. Pretend firefox as chrome makes it works perfectly. They lock the community thread and fixed that after several days I found the finding and post it there. Shame on you, google.
Oh my god. I knew it was inserting a line break when I hit enter but I didn't realize it was a FF only issue. gdi Google.
Re: Chrome phasing out support for User-Agent
#125User-agent is super useful to human people. But corporate people don't have a use for it. They will get that information via running arbitrary code on your insecure browser anyway. So, because mega-corps now define the web (instead of the w3c) this is life. But it doesn't have to be. We don't have to follow Google/Apple-Web standards. Anyone that makes and runs websites has a choice. And every person can simply choic…
Re: Chrome phasing out support for User-Agent
#126Re: Chrome phasing out support for User-Agent
#127Earlier quoted context omitted.
It actually insert a line break on enter, make it invisible and can't be deleted only on firefox. Pretend firefox as chrome makes it works perfectly. They lock the community thread and fixed that after several days I found the finding and post it there. Shame on you, google.
Oh my god. I knew it was inserting a line break when I hit enter but I didn't realize it was a FF only issue. gdi Google.
(That's not snark - I really don't get it. They don't appear to mind people talking negatively about a lot of other stuff they get up to. Maybe lingering antitrust fears from the 90's MS suit?)
Re: Chrome phasing out support for User-Agent
#128The weird thing about this is that the only company I've seen doing problematic user-agent handling in recent years is Google themselves. They have released several products as Chrome-only, which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent. Same with their search pages, which on mobile were very bad in every non-Chrome browser purely based on user age…
I had been thinking recently as I've been using Firefox more that Google maps had got clunky. With a little fiddling prompted by your comment, it turns out Maps sniffs specifically to reduce fluid animations on Firefox (and probably some other browsers).
Re: Chrome phasing out support for User-Agent
#129The weird thing about this is that the only company I've seen doing problematic user-agent handling in recent years is Google themselves. They have released several products as Chrome-only, which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent. Same with their search pages, which on mobile were very bad in every non-Chrome browser purely based on user age…
If you have the new Chromium-based Edge ("Edgium") installed: the compatibility list at edge://compat/useragent is really interesting. Edgium pretends to be Chrome towards Gmail, Google Play, YouTube, and lots of non-Google services; on the other hand, it pretends to be Classic Edge towards many streaming services (HBO Now, DAZN, etc.) because it supports PlayReady DRM, which Chrome doesn't. [Edit] Here is the full l…
I see lots of people who have to use edge on order to get 4k content from Netflix; presumably because of the DRM issues.
Re: Chrome phasing out support for User-Agent
#130This is a good idea, and is something I've thought of for a while; the user agent header was a mistake from both a privacy and a UX perspective. Ideally, web browsers should attempt to treat the content the same no matter what device you are on. There shouldn't be an iOS-web, and a Chrome-web, and a Firefox-web, and an Edge-web; there should just be the web. In which case, a user-agent string that contains the browse…