Difference ESR 115 and 141 with position: fixed (site using has selector which is not enabled in esr115)
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: gerard, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
Steps to reproduce:
I have an old PC with Win7 and Firefox 115.30.0esr (64-bit) (latest version from 11 november 25) and this website cultuursmakers.be has problems aka differences with Firefox 141.0.3 (of my Android tablet) and other browsers such as Chrome.
Actual results:
The green heading block overlaps and hide the upper part of the content block.
For example, if you select inloggen (log in), then you see that the user name (naam) is not visible and only the box for the password is shown.
Expected results:
Both name and password input boxes should been visisble.
Work around:
Right click on the header and select Inspect.
In the Inspector (html column) select the header tag.
In the Inspector (css column) uncheck in the '.header.--fixed' selector the line 'position: fixed;'
Now the content block shifts down and all content is visible as it should.
|
||
Comment 1•11 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Panning and Zooming' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Updated•11 months ago
|
|
|
||
Comment 2•11 months ago
|
||
I tried the steps on my android phone (no android tablet), and I was able to see both the username and password field.
Yes, that is what I said. On the recent Firefox Version 145 for Android and its predecessors like 141, and also other browsers, it works correct. It is the recent Firefox ESR edition that has the problem.
|
|
||
Comment 4•11 months ago
|
||
Sorry for misunderstanding.
I tried ESR 115 on a desktop machine. I was still able to see the username and password field. Is that where you are seeing the problem?
Perhaps you could try in a fresh profile to see if it still happens?
I tried a new created fresh profile and it works as it should.
So, something in my current profile is messing with the appearance of the website and the bare Firefox ESR 115 works OK.
Any suggestions where to start for finding the culprit?
|
|
||
Comment 6•11 months ago
|
||
If you upload a copy of your about:support here it lists important changes to your profile from a fresh profile (addons, preferences). We can both look it over and see what things are different and suggest what might be the culprit.
Maybe, I was a little bit too early in saying it was OK.
In the fresh profile I found the problem on these URL:
https://hoeilaart.cultuursmakers.be/login
https://hoeilaart.cultuursmakers.be/activiteiten/detail/2611/musical-my-fair-lady-volzet
Can you verify?
|
|
||
Comment 8•11 months ago
|
||
Thanks I can reproduce that.
One of the changesets in here (which landed after 115 branched)
is what fixed it.
|
|
||
Comment 9•11 months ago
•
|
||
I think it is bug 1853701
https://hg-edge.mozilla.org/mozilla-central/rev/dd890d993c3039c40d9a50218bd3284a9810cc85
If I set the pref layout.css.has-selector.enabled to true then that fixes the issue.
Bug 1858743 is the one that enabled that to release.
You can try layout.css.has-selector.enabled to true to work around the issue, however that means you are enabling code that was not finished (why the pref was not enabled), so you might run into bugs, crashes or other issues.
|
|
||
Updated•11 months ago
|
|
||
Updated•11 months ago
|
|
||
Comment 10•11 months ago
|
||
Yeah... That's not great, :has shipped in 121, so uplifting to ESR 115 isn't exactly possible..
|
|
||
Comment 11•11 months ago
|
||
Yeah, there's a fair bit of sweeping changes over time that makes it intractable for uplift to ESR 115.
FWIW the recently released ESR should support it.
|
Reporter | |
Comment 12•11 months ago
|
||
I have updated today to 115.31.0 esr (64-bit). The problem was also there, but it was resolved by setting layout.css.has-selector.enabled to true in about:config .
I did not remark any other consequences.
Many thanks to Timothy Nikkel for this resolution.
|
|
||
Comment 13•11 months ago
|
||
(In reply to David Shin[:dshin] from comment #11)
FWIW the recently released ESR should support it.
Unfortunately I believe for the machine in question ESER 115 is likely the newest Firefox it can get.
Description
•