3 ms·
I wish they'll say Tablet on tablets instead of Mobile, like Firefox will do: https://developer.mozilla.org/en/Gecko_user_agent_string_reference#Mobile_and_Tab
by bergie 15y ago
I wish they'll say Tablet on tablets instead of Mobile, like Firefox will do:
https://developer.mozilla.org/en/Gecko_user_agent_string_reference#Mobile_and_Tablet_indicators https://developer.mozilla.org/en/Gecko_user_agent_string_ref...
- gcp 15y agoI wish website developers would stop using UA sniffing. WTH do you care whether it's a Tablet or a phone? Don't you frecking care for the resolution instead? What the heck are you going to do on a Galaxy Note? Are you serving the same site on a Wildfire S as you are serving a Galaxy Nexus? 9 times out of 10, whenever a webdev tries to be "smart" and serves up a mobile version of a website, I don't want it because it's a crippled, badly working knockoff of the real thing. Chrome and Firefox on Android are real browsers and can display the full site, so stop feeding them this crap. I heard there's a room in hell where you are forced to use various Android browsers on various mobile devices all day.
- Zikes 15y agoThis is why I'm thankful for the new responsive web design initiative. Same page, same resources, no more or less round-trips, just a different layout tailored to your screen size and density.
- aphexairlines 15y agoMajor e-commerce product detail page html for PC: 240775 bytes For smartphone: 15903 bytes For old phones (mostly text): 2369 bytes Server-side device detection does make a difference here, and in other footprints (initial external resources, backend services) as well.
- gcp 15y agoI think you just confirmed my complaint that smartphones get a crippled site. I don't think UA sniffing tells you what connection I am on, right?