You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just waisted way too much time debugging why safe areas on iOS was 0px. Turned out the viewport meta tag was missing the "viewport-fit=cover" property, which is mandatory for safe areas to work on iOS.
It was confusing, since the app actually rendered perfectly edge-to-edge without "viewport-fit=cover", so I didn't suspect anything wrong with the viewport.
Not every project is initialized by default with "viewport-fit=cover" set in the meta tag, so it would be nice if it were added to the docs as a requirement for iOS to work.
#22 was probably due to the same thing (their Nuxt setting overriding the original meta tag, which probably had "viewport-fit=cover" set).
The text was updated successfully, but these errors were encountered:
Yes, for web and iOS to be able to make use of the env variables, you should add "viewport-fit=cover" as the meta tag value. To be clear: that's always true, and not only when using this plugin. I added it to the docs
Just waisted way too much time debugging why safe areas on iOS was 0px. Turned out the viewport meta tag was missing the "viewport-fit=cover" property, which is mandatory for safe areas to work on iOS.
It was confusing, since the app actually rendered perfectly edge-to-edge without "viewport-fit=cover", so I didn't suspect anything wrong with the viewport.
Not every project is initialized by default with "viewport-fit=cover" set in the meta tag, so it would be nice if it were added to the docs as a requirement for iOS to work.
#22 was probably due to the same thing (their Nuxt setting overriding the original meta tag, which probably had "viewport-fit=cover" set).
The text was updated successfully, but these errors were encountered: