sedonarota.verlacarta.com - Navigation bar from the header is missing
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:5)
People
(Reporter: ctanase, Unassigned)
References
()
Details
(Keywords: spain, webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:site-broken configuration:general affects:all branch:release diagnosis-team:layout user-impact-score:200
Attachments
(1 file)
|
1.47 MB,
image/png
|
Details |
image.png
Environment:
Operating system: Android 14/Windows 10
Firefox version: Firefox Mobile 136.0/138
Steps to reproduce:
- Go to https://sedonarota.verlacarta.com/
- Click on the down arrow.
- Observe the page.
Expected Behavior:
The navigation bar is displayed.
Actual Behavior:
The navigation bar is missing.
Notes:
- Workaround: Click on cocktail and go back
- Reproduces on both mobile and desktop
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/149958
|
Reporter | |
Comment 1•11 months ago
|
||
|
||
Updated•11 months ago
|
|
||
Updated•11 months ago
|
|
||
Comment 2•11 months ago
|
||
I can reproduce in a fresh profile with Nightly 138.0a1 2025-03-21 and with release 136.
For some reason I can't reproduce in my main browsing profile, though. Not sure if that's a race condition or some setting I have enabled.
|
|
||
Comment 3•11 months ago
•
|
||
Aha, it's -webkit-fill-available -- this works properly if I have that pref toggled to true. (And it's specifically a rule for html, body { height: -webkit-fill-available} that matters here -- that needs to be set and honored before you click the downarrow button, presumably because the site does some geometry measurement and ends up broken or working depending on the height that it measures.)
|
|
||
Comment 4•5 months ago
•
|
||
This is fixed by the patch that I've just landed in bug 1988938. I just tested with the URL, in a local build with that patch applied, and I confirmed that it's fixed there (and that the issue comes back if I then turn off the pref that bug 1988938 enabled, in that build).
--> Closing as fixed by bug 1988938, and swapping in bug 1988938 as the platform-bug here rather than bug 1872755 (which remains open and tracks broader support that's not needed here).
Description
•