Quote:
Originally Posted by microbet
Unless there's something totally wrong with me, CSS and Chrome on android is just really erratic - really buggy.
Lol welcome to the terrordome. Choose your weapon: Samsung, Pixel, LG, apparently there's something called One Plus? Just kidding - you'll need to buy all of them as they all have their own weird quirks. Also you can't upgrade the OS until the carrier lets you. Every Android is a special snowflake combo of device, OS, and carrier-specific integration.
I'm sure it's better now but back in the day before every major project we'd look up the most popular phones and what OS they were mostly stuck on. Then we'd spend a lot of money on those. Upgrade one when the time came, but not upgrade another (which means the testers had to remember to say No every single time it popped up - no undoing).
We also had to support Chrome and Android native browser which Samsung insisted on never letting go of (does that POS still exist?). Both used the Chrome engine but Chrome was on like v39 while Samsung Galaxy with the latest upgrades was on v28. Fun fun bugs.
I literally had code that was like if (androidOS < 5.1 && browser !== 'Chrome' && manufacturer === 'HTC' && carrier === "AT&T"). But of course it wasn't that easy because each of those had to be derived from the cryptic user agent string. So much so there was some open source project to categorize all of the user agent strings and identify the devices, OS, browser, carrier, size, etc. The XML file it generated was like 20 GB. Here it is. I guess it's not open-source anymore:
http://wurfl.****************/ Wtf why is so urceforge . net blocked?
I could always tell when we were close to actually finishing a project when some poor front end dev had an array of Androids scattered around his/her desk for a week and they're the last one out at night. Before that event I knew "almost done" was just talk.
Last edited by suzzer99; 03-07-2019 at 11:04 PM.