I don't think I have ever seen a more inaccurate summary in my life. Holy cow this is off the rails:
No, a user agent doesn't retrieve or render anything. It is a string, just some text, that say what browser it is and what version, and often lists similar browser rendering engines that it should be compatible with. It is literally just a description of the browser. The server then determines what to send back based on that.
The big change is that Safari on iPad now reports, via the user agent, that it is MacOS, not iOS, and they've updated how it handles events that can have conflicts on a touch based device.
Safari on iOS devices has been desktop class (excluding PlugIns) from the start. The golden era for iOS web browsing for me was the first nine months to a year after the original iPhone was released. Websites were always rendered as the Desktop version web during that period but then designers changed their sites to recognise the iPhone as a mobile device and ‘forced’ the mobile version of the site for iOS devices as a default.Can anybody explain why, from a technical perspective, safari on the iPad hasnt been a desktop class browser?
Lol, your reaction is off the rails if anything. Safari's user agent can be used by a web server to choose variants based on the known capabilities of a particular version of client software - in this case macOS versus iOS. So the user agent string causes a different retrieval of the site, which gets rendered differently because it's desktop but now with touch interactions. Thanks, Apple.
Go and cool down.
Did they make under the hood improvements to Safari for the desktop experience or are they just returning a different browser agent so that websites think its the desktop version of Safari?
This whole narrative is a bit frustrating. iPhoneOS 1.0 promised a "desktop class browser" back in 2007. Look at this press release for example:
View attachment 841353
https://www.apple.com/newsroom/2007/01/09Apple-Reinvents-the-Phone-with-iPhone/
The whole point from the very beginning of iPhone was that the browser was a proper real browser and better than that WAP crud we had before. Then mobile optimization happened and we seemed to have ended up with something better than WAP but still not the promised desktop-class browser.
We keep being promised desktop-class browsing, but that seems to be elusive. What gives?
Can anybody explain why, from a technical perspective, safari on the iPad hasnt been a desktop class browser?
This whole narrative is a bit frustrating. iPhoneOS 1.0 promised a "desktop class browser" back in 2007. Look at this press release for example:
View attachment 841353
https://www.apple.com/newsroom/2007/01/09Apple-Reinvents-the-Phone-with-iPhone/
The whole point from the very beginning of iPhone was that the browser was a proper real browser and better than that WAP crud we had before. Then mobile optimization happened and we seemed to have ended up with something better than WAP but still not the promised desktop-class browser.
We keep being promised desktop-class browsing, but that seems to be elusive. What gives?
Awesome! I was about to ask if wix works!!!And YES! Wix website editing works!
AWESOME!
I tried to use iCab mobile on my iPad before to edit my wix blog posts but too many glitches so I gave up on using itSafari on iOS devices has been desktop class (excluding PlugIns) from the start. The golden era for iOS web browsing for me was the first nine months to a year after the original iPhone was released. Websites were always rendered as the Desktop version web during that period but then designers changed their sites to recognise the iPhone as a mobile device and ‘forced’ the mobile version of the site for iOS devices as a default.
If I need to use a desktop site on my iOS devices I currently use the iCab Mobile browser which has user agent spoofing options.
It's embarrassing that I needed to ask this, considering I do some (front end)w development on the side. But thank you for this explanation I totally understand this now.All browsers advertise a 'User Agent' when visiting a website. It tells the server what kind of browser it is, what OS you're running, the versions, etc. Traditionally, websites would have a desktop version and a mobile version and they'd use this User Agent string to determine which one to serve up. Lots of those websites lump all smartphones and tablets in the same category and serve the mobile version to all. What Apple is doing is changing that User Agent string so those types of websites will, hopefully, instead serve up the desktop version. They're also doing other things so those desktop versions work better on a touch interface but that's the gist of it.
It's not so much that Apple is fixing a defect in their browser. It's more that Apple is working around a problem created by companies and website developers that don't develop their sites to work properly on tablets and instead still treat them like phones with small screens.
This will probably only affect websites that still rely on a User Agent, which a surprising number still do. The modern way of doing this is to ignore that string and instead adopt responsive web design practices where you don't have a "desktop website" and a "mobile website". You have a single website that's designed to work well with any sized screen. You start on the smallest screen you want to support and make your site work 100% correctly on it. You then make the screen bigger until your site breaks and fix it to work at this resolution. Keep doing this until it works at all resolutions. This change that Apple is making most likely won't have much of an affect on those sites as they should already work well on an iPad (assuming the web developers weren't idiots which is entirely possible).
This whole narrative is a bit frustrating. iPhoneOS 1.0 promised a "desktop class browser" back in 2007. Look at this press release for example:
View attachment 841353
https://www.apple.com/newsroom/2007/01/09Apple-Reinvents-the-Phone-with-iPhone/
The whole point from the very beginning of iPhone was that the browser was a proper real browser and better than that WAP crud we had before. Then mobile optimization happened and we seemed to have ended up with something better than WAP but still not the promised desktop-class browser.
We keep being promised desktop-class browsing, but that seems to be elusive. What gives?
They now return a user agent saying they are macOS rather than mobile or iOS, and they’ve updated how the iPad responds to many events to help with conflicts between touch based and mouse based interfaces. There is a pretty good video on it from WWDC.
This whole narrative is a bit frustrating. iPhoneOS 1.0 promised a "desktop class browser" back in 2007. Look at this press release for example:
View attachment 841353
https://www.apple.com/newsroom/2007/01/09Apple-Reinvents-the-Phone-with-iPhone/
The whole point from the very beginning of iPhone was that the browser was a proper real browser and better than that WAP crud we had before. Then mobile optimization happened and we seemed to have ended up with something better than WAP but still not the promised desktop-class browser.
We keep being promised desktop-class browsing, but that seems to be elusive. What gives?
Is this video available to the public? If so, can you share a link?
So will users be able to have per website settings? And will those settings to sync across all your devices?
Apple really made major leaps and bounds this year so far.