Status Update
No update yet.
Comments
ye...@google.com
This bug has led to a large number of gardened builds failing in the last 7 days. List of gardened build failures caused by this cluster can be viewed at:
or in LUCI Analysis and grouped by builders:
Please consider the following strategies to mitigate the impact from this issue which are rated in order of resolution preference:
1. Resolve the underlying test issue.
2. Move the flaky test from Critical Builders to FYI Builder
3. Disable test (least desirable as it reduces test coverage) and add a Test-Disabled label to this issue. The disabled tests might continue running in reviver builders (go/test-reviver), see config [1] for a list of supported builders.
When investigating this failure, you may identify this bug is too broad (encompasses multiple different issues) or too narrow (only captures one part of a larger issue). If this applies, you can combine issues[2] or split issues[3].
Links:
[1]
[2]
[3]
Why LUCI Analysis posted this comment:
ma...@googlemail.com
pe...@google.com
Thank you for providing more feedback. Adding the requester to the CC list.
ma...@googlemail.com
Screenshot while skyping as you can see. ;)
ma...@googlemail.com
Hope, this can be fixed soon! :)
ye...@google.com
@jinsukkim, Could you please look into this issue? If it is not related to you, kindly help us reassign it to the concerned developer. Thank you in advance!
ye...@google.com
ji...@chromium.org
If I understand the issue correctly:
Is this correct?
Can't repro on my devices. I see the red bottom nav all positioned at the bottom of the screen.
- Chrome 131.0.6778.200/Android 12; Pixel 3 SP1A - ok
- Chrome 124.0.6367.82/Android 14 - ok
- Local build/Android 14 - ok
I don't know if we have any live experiment that might misplace the fixed-position element on the page load either.
ji...@chromium.org
Not really sure who to route this too... cc'ing twellington@ for help
tw...@google.com
tw...@google.com
cc'ing bokan@ who has also done somewhat recent work on viewport sizing (wrt to keyboard).
The video in #2 doesn't seem to contain the issue.. yerrar@google.com - were you able to repro?
From #5, this may be OEM specific (original report was from a Samsung device)
tw...@google.com
ye...@google.com
When I keep the device orientation in portrait mode, all fixed elements appear as expected. However, when I change the device orientation to landscape mode, the page becomes un-scrollable, and the fixed elements are not visible. I verified this issue on both Pixel and Samsung devices.
tw...@google.com
ye...@google.com
Hi @jinsukkim, just a gentle reminder to check if you're able to reproduce the issue with the additional details provided in #12. Thank you!
bo...@chromium.org
This sounds a lot like:
tw...@google.com
Re #14 -- Jinsuk is OOO for two weeks starting this evening; unfortunately suspect this fell off his radar and that he didn't have time look at it today when doing wrap-up / prep for his OOO.
Thanks bokan@ for the cross-reference with
Description
Steps to reproduce the problem
Problem Description
When manually entering a URL in Chrome/Android (from the start page or address bar), fixed-position elements (position: fixed) that are anchored to the bottom of the viewport (bottom: Xpx) are rendered below the visible viewport, causing them to be partially or completely hidden.
This issue occurs specifically during initial page load after typing the URL manually into the address bar. Once the user interacts with the page (e.g., taps anywhere, scrolls, or resizes the viewport), the position of the fixed elements is recalculated, and the issue resolves itself.
Additional Comments
Problem occurs with every page I wrote that have a css element placed near the bottom of the viewpoint. It doesn't happen in Windows Chrome or Windows Edge. Android Edge not yet tested. It doesn't happen if webpage is visited through Google search or other link, only when entering URL diretly from default start page.
Summary
Fixed elements appear below the viewport when manually entering the URL in Chrome/Android
Custom Questions
Example URL:
Does the problem occur on multiple sites?
Yes - Please describe below
Is it a problem with a plugin?
Not sure - I don't know
Does this work in other browsers?
Yes - This is just a Chromium problem
Additional Data
Category: Content
Chrome Channel: Stable
Regression: N/A