Is there a bug in Chrome for Android for the position fixed grid children?
Hi everyone!
Does anyone know if there is any recent change in Chrome for Android generating this weird behaviour in the position fixed grid children?
As far as I know (and I think it was behaving this way a few weeks ago), when you set a position fixed to an element, it is removed from the normal document flow, so if I have a grid child and I set a position fixed to it, it should be removed from the grid container and therefore, not being affected for its constraints. This is how the grid children are behaving in all the browsers and devices except for one case: Android Chrome browsers (not even Chrome browsers from other devices or OS).
I have an example here which you can try with a Chrome browser from an Android device to see how it behaves differently:
https://codepen.io/btous/pen/zYbgEyz?editors=0100
8 Replies
Works as it should on my end. Added a border to the div.grid to see where it ends, ticked the "fixed" box and the liteblu thing fixed itself at the very top.
Is it taking up the entire width of the screen when it's fixed? It should
Yes.
The weird behaviour appears only in Chrome Browsers in Android devices. This screenshot seems from a desktop window to me. Could it be?
Yes, desktop Chrome. Linux.
...Chromium, not that linux fork.
So it is working as expected. As I said, the weird behaviour is only appearing in Chrome browsers on Android
Too lazy to look now, sry.