NEW305546
REGRESSION (Safari 26.2): Status bar background is replaced with shadow on soft navigation 
https://bugs.webkit.org/show_bug.cgi?id=305546
Summary REGRESSION (Safari 26.2): Status bar background is replaced with shadow on so...
hei
Reported 2026-01-15 01:06:40 PST
Created attachment 478030 [details] Demo web app and videos This behaviour is reproducible in both Home Screen Apps and Safari. When there is an HTML element fixed to the top of the page, with a different background color than the body element, the status bar background is set to the opaque color of the fixed element's background. This is a popular use case for making fixed nav bars that blend in with the status bar, both for web pages and Home Screen Apps. When soft-navigating (i.e. swiping back or SPA routing) in Safari 26.2, the status bar background is replaced with a shadow based on the background color of the page. This breaks the illusion of the unified nav and status bar, and the content being visible behind the mostly transparent status bar has a jarring effect. Trying to work around this by setting the theme-color with a meta element has no effect. Safari 26.2 on macOS Tahoe display the same bug. See attachments for videos and demo page.
Attachments
Demo web app and videos (80.52 MB, application/zip)
2026-01-15 01:06 PST, hei 		no flags
Details
web page demo (4.47 KB, application/zip)
2026-01-15 01:19 PST, hei 		no flags
Details
web page demo (4.60 KB, application/zip)
2026-01-15 05:08 PST, hei 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
hei
Comment 1 2026-01-15 01:19:16 PST
Created attachment 478031 [details] web page demo
hei
Comment 2 2026-01-15 05:08:49 PST
Created attachment 478033 [details] web page demo
Radar WebKit Bug Importer
Comment 3 2026-01-16 19:19:58 PST
<rdar://problem/168340980>
pascoe@apple.com
Comment 4 2026-03-11 11:25:03 PDT
Pull request: https://github.com/WebKit/WebKit/pull/60377
hei
Comment 5 2026-06-01 00:33:55 PDT
No action here for a couple of months. Do you guys have any plans to merge the fix for this?
Note You need to log in before you can comment on or make changes to this bug.