1 Correct answer
In iOS you cannot turn of the user zoom anymore, what Apple says is -
To improve accessibility on websites in Safari, users can now pinch-to-zoom even when a website sets user-scalable=no in the viewport.
As for getting it to be 1px = 1px, you can only do this by using the correct media-query, complete with using the correct resolution. Get it wrong and the iOS Safari browser, (and every other browser) will automatically make the page fit.
That is why I said it is an almost impossible task. Plus d
...
28
Replies
I post weird threads that almost always accidentally uncover something the experts didn't yet know 
if they help more people than just me piece stuff together, all the better.
There's an infinity of tutorials out there on how to handle desktop vs mobile, many seem to involve using 2 stylesheets. I have no issues with this solution after learning that Apple is still trying to make the decisions for us. Have they done ANYTHING right since Jobs died?
But I digress. What I'm really asking is if you have a tutorial to recommend that isn't dated 2009 and contains the most recent info available. 
Whether it uses multiple stylesheets, if/than statements, or something else entirely. Thanks!
I haven't seen a tutorial I would recommend on anything to do with front-end web development, since the original iPhone came out.
99.9% is mainly based on someone personal opinion, or on ideas that when looked into are so full of holes one could use them as a colander. Then of course everything changes with every update, (as we just found out ) as with better css support more becomes possible.
It may sound strange, even after almost 10 years of developers trying to find the best strategy for handling responsive sites, but do what you think is best for you. Even if you develop with 2 or more style sheets, you can always move everything to 1 file once you are ready to commit to a live site.
Be careful if you wish to use a pre/post-processor though, as no one type has yet to become what most people use, and browser support for css solutions for things like css variables, has improved dramatically, and more is yet to be implemented. That means the use of pre/post-processors may not be necessary in 4-5 years time.
https://forums.adobe.com/people/Under+S. wrote
So... diversity or segregation -- What say you?
No comment 
The problem unfortunately is only going to get worse over the next few years, as more people are starting to browse the internet using smart-tv's (incl. 4k) and 4k game consuls.
pziecina wrote
The problem unfortunately is only going to get worse over the next few years, as more people are starting to browse the internet using smart-tv's (incl. 4k) and 4k game consuls.
The auto-zoom will become more popular, I get that. At 4K or anything close to retina display, a 1000 pixel-wide website would occupy barely over 3 inches of width. Who can read that? The internet was built on pixel values. Perhaps that will change to something else now that we're essentially moving into the vector age of no fixed pixels (I even predict a future where your average $600 Nikon/Cannon camera will take vector photos, not just pixel ones, by essentially redrawing everything with ridiculous precision in vector format -- at first, it will be like Polaroids, you'll have to wait a few seconds to see the photo, even on-screen, because billions of calculations -- but I digress).
I've yet to hear a better solution than 2 sets of classes, one for portrait / small screens, and one for landscape / large screens. Web design was never about recreating the same exact experience on all viewports, that's a madman's mission. There is always going to be a "sweet spot" where one specific resolution really puts the website in its best light in the beholder's eye, but seldom will everyone agree on which one that is (some people LIKE artsy, some people prefer straight-forward, and some people like a mix of both).
That being said, which of the 2 methods I'm suggesting is the one you CSS deities prefer, or consider more sound today?
Interesting notes. If I'm using PHP (mostly includes) does that open other doors that might help me I.D. mobile devices w/out resorting to resolution? Perhaps PHP can help sniff out the fact that it's a mobile device some other way? Like a hidden "I am a mobile device" tag somewhere in its OS? (Yes, I realize I'm hoping against hope, here.) I ask because I'm not really a programmer, I'm a designer who learned as much about programming as they needed along the way.
Also, Bob, could you share your device-identifying script with us?
AdChoices