Earlier quoted context omitted.
If your site doesn't use JS, you don't need features. Just use responsive HTML.
How do you handle browsers that render HTML differently?
Chrome phasing out support for User-Agent
271–280 of 329 posts
Re: Chrome phasing out support for User-Agent
#272https://groups.google.com/a/chromium.org/forum/#!msg/blink-d...
Re: Chrome phasing out support for User-Agent
#273Personally, I would like to drop the line completely and not send the key at all, but it's a start.
Re: Chrome phasing out support for User-Agent
#274Re: Chrome phasing out support for User-Agent
#275Earlier quoted context omitted.
Wait til you see how amazing the experience can be with Usenets...
How do I get into using Usenet?
Re: Chrome phasing out support for User-Agent
#276Earlier quoted context omitted.
Last time I used piratebay, I saw a lot of porn and malware/scam ads. I had to find and install a torrent client. Then I had to make sure I was downloading a movie that had enough seeders. And then I couldn't watch the movie until (and if) the download finished. When I use netflix, I have a much better experience.
You can use webtorrent - https://webtorrent.io/
Re: Chrome phasing out support for User-Agent
#277Earlier quoted context omitted.
It's the exact opposite. Without User-Agents, sites need to depend on feature detection, and closing the feature discrepancy between Chrome and other browsers is more complicated than just spoofing your UA to get Google to serve you functioning versions of their products.
I interpreted your parent's comment differently; namely, if Google's developers can't do User-Agent detection, then internally even they will have to improve how they develop (eg. via feature detection), making their products more compatible with other browsers. Many people assume Google, as an upper-level business decision, purposely makes products work better on Chrome in order to vendor-lock users to the browser.…
So Google developers don't need to improve feature detection - that part is working fine already.
Re: Chrome phasing out support for User-Agent
#278Good. User-agent strings are a mess. Here is an example of a user-agent string. Can you tell what browser this is? Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13 How did they get so confusing? See: History of the browser user-agent string https://webaim.org/blog/user-agent-string-history/ Also, last year, Vivaldi switched to using a user-agent st…
Re: Chrome phasing out support for User-Agent
#279Any idea on how to identify devices then? We currently check the user agent to to send a new code when an user logs in from a new device. How would you do this without user agent?
Re: Chrome phasing out support for User-Agent
#280Earlier quoted context omitted.
I had been having an issue with Google Sheets and Firefox that the app decides to change row height randomly. On Firefox only. Obvious solution to which being...
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.