fbpbdmin is experiencing an issue with an iOS Safari browser not loading the mobile version of a theme component. The component is defined with different CSS and HTML for desktop and mobile. On iOS Safari, it loads the desktop version instead of the mobile one.
merefield suggests confirming the issue by forcing the mobile view with the URL query string ?mobile_view=1. fbpbdmin tests this and finds that the issue persists, even after updating to iOS 17.2.1.
However, when using the query string ?mobile_view=1 on the iOS Safari browser, it loads the mobile version correctly. fbpbdmin plans to create a GitHub repository to make it easier for others to reproduce and debug the issue.
merefield notes that on iOS 17.3, the mobile version of the theme component loads correctly without needing the query string.
I have a theme component, it has css and Head defined for both Desktop and mobile.
on mobile, a shape is defined smaller for space.
it works nicely on chrome, firefox on iphone, but in safari, it loads the desktop version instead.
the safari browser is not loading desktop version of the site.
someone saw this issue ? iOS mobile safari does not report itself as a mobile browser ? or …
it is safari on iOS 17.1.2, when load the component, it shows the big shape defined for Desktop
just updated iOS to latest 17.2.1, same.
on the same device, if open it using chrome or firefox, it shows the small shape defined for Mobile
on desktop browser, if view it https://example.com?mobile_view=1, it shows the small shape defined for Mobile.
I suspected there is something my safari browser loads the desktop content, but it is not, say it loads the mobile layouts, not desktop version.
did not notice this before, maybe I was using chrome most time on iphone…
to reproduce, I made this simplifed version to show the issue.
this sample code below basically show a big red circle in desktop browser, a smaller one in mobile browser.
after install this component, you could see
it shows the small circle on iphone chrome/firefox, this is expected
but a big one with safari, as defined for desktop browser. this is not expected