Bug 306465

Summary: viewport-fit=cover is not respected on iOS in portrait mode
Product: WebKit Reporter: Bramus <bramus>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: thorton, webkit-bug-importer, wenson_hsieh
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Safari 26, Portrait Mode, Page with viewport-fit=cover
none
Safari 26, Landscape Mode, Page with viewport-fit=cover none

Bramus
Reported 2026-01-28 13:50:11 PST
Created attachment 478183 [details] Safari 26, Portrait Mode, Page with viewport-fit=cover When you set `viewport-fit=cover` in the viewport meta tag, you are instructing the browser to have the viewport scale so that it fills up the entire viewport. This works on iOS in Landscape mode, but not in Portrait mode. I would have expected that in portrait mode, the green bars would be painted against the top and bottom edges of the screen. (Authors should then also use the safe-area insets to prevent content from painting underneath the unsafe regions) Demo Page: https://interop-2022-viewport.netlify.app/individual/safe-inset-areas/viewport-fit-cover Use-case: have a bottom-fixed toolbar that is opaque and whose color extends into the region where the address bar is rendered.
Attachments
Safari 26, Portrait Mode, Page with viewport-fit=cover (236.20 KB, image/jpeg)
2026-01-28 13:50 PST, Bramus
no flags
Safari 26, Landscape Mode, Page with viewport-fit=cover (256.90 KB, image/jpeg)
2026-01-28 13:50 PST, Bramus
no flags
Bramus
Comment 1 2026-01-28 13:50:32 PST
Created attachment 478184 [details] Safari 26, Landscape Mode, Page with viewport-fit=cover
Radar WebKit Bug Importer
Comment 2 2026-01-28 17:32:45 PST
Bramus
Comment 3 2026-02-05 07:42:57 PST
Supporting `viewport-fit=cover` would solve user complaints like https://modernwebweekly.substack.com/i/179552520/the-curious-case-of-the-status-bar-on-ios-26, because with `viewport-fit=cover` authors gain control over things.
Note You need to log in before you can comment on or make changes to this bug.