The toolbar library bookmarks and history panels have a scrollbar no matter how short they are
Categories
(Firefox :: Menus, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox86 | --- | unaffected |
firefox87 | --- | unaffected |
firefox88 | + | wontfix |
firefox89 | + | verified |
firefox90 | --- | verified |
People
(Reporter: ailea, Assigned: mconley)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: helpwanted, regression, Whiteboard: [proton-hamburger-menu][priority:2b] [proton-uplift])
Attachments
(4 files, 2 obsolete files)
Tested with:
Nightly 88.0a1 (2021-03-01)
Tested on:
Windows 10
MacOS 10.15
Ubuntu 20.04
Preconditions:
In about:config, set browser.proton.appmenu.enabled = true
Steps:
- Launch firefox and open the Bookmarks or History (from the Toolbar Library).
Actual result:
There is a scrollbar displayed no matter how long or short the list of recent bookmarks/history is.
Expected result:
The scrollbar should not be displayed if the Bookmarks/History Panel is shorter than the screen length.
Notes:
- The issue is reproducible with and without Proton enabled.
- This is not reproducible in Release 86 or Beta 87.
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Do you have multiple displays? Are they running at different DPIs? Have you changed your system font sizes? Any kinds of these details will help uncover what is going on here.
Also, are you saying that the bug goes away if you set browser.proton.appmenu.enabled = false?
Reporter | ||
Comment 2•4 years ago
|
||
Hi Jared,
I have dual monitors with the same resolution, but this is happening using one monitor as well. Also it is reproducible on Macbook macOS 10.15 without any other monitor/display connected. I did not changed the system fonts or other OS settings. I can reproduce it with new clean Fx profile.
And for the last question, the issue is reproducible with proton pref disabled (set to false) as well. I attached here the about:support, maybe it helps.
Comment 3•4 years ago
|
||
I can reproduce this on my Windows machine (Win10, 150% dpi, single screen, no text size changes from the default), and this regressed with bug 1688960.
From a very quick look at the patch, I expect 1 of 2 root causes: a rounding error of sorts, or the font size the header inherits is different between the off-screen place where we check its height compared to the main panel where we then insert it (as the new styling uses font-size: inherit
in a few different places).
Mike, can you take a look? If you struggle to repro on Windows please let me know and I can take another look myself.
In terms of priority, I think this is a polish issue that we should try and get fixed in time for 88 - it's not critical, but it does look a bit naff as-is.
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
[Tracking Requested - why for this release]:
With all that's going on, I don't want to lose track of this. It's a polish-y issue, but in some pretty front-and-center UI, so we should get to this before the uplift.
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information
Assignee | ||
Comment 6•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Comment 7•4 years ago
|
||
Hey Gijs,
I noticed a similar bug when applying mtigley's patch for bug 1694277. The patch I've attached seemed to fix it. Does it also fix the Library case that you were able to reproduce?
Comment 8•4 years ago
|
||
Unfortunately no. I left a more detailed comment on phab, let's continue there.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 9•4 years ago
|
||
Hey rtestard, do you think this is sufficiently important for me to look at (it's reproducible with / without Proton on 88+) instead of Proton work? Or can we ship 88 with this regression?
Comment 10•4 years ago
|
||
This one seems like a medium P2 so marking [priority:2b]
We should focus on P1 or [priority:2a] priorities instead - OK to let this regression go with 88 even if it's a shame but we have to be realistic on what can be done in a given time :(.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 11•4 years ago
|
||
This is also reproducible on MacOS for the Bookmarks and History panels toggled from the toolbar library button.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 13•3 years ago
|
||
Coming back round to this. I too am able to reproduce this in macOS now. Investigating.
Assignee | ||
Comment 14•3 years ago
|
||
This is pretty strange. It seems that the .panel-subview-body
element is getting an intrinsic height that doesn't seem to take into account the h2
's padding and non-default font-size. If I reset the font-size to the default, then the scrollbar goes away. It's truly odd, and I can't really explain it.
I've also noticed that there seems to be a minimum height on the subheader of 24px which was not helping.
Interestingly, the problem seems to go away if I make the .panel-subview-body
element use the CSS flexbox model instead of the XUL flexbox model. That's not without risk, so I don't think this is something we'd want to consider uplifting.
Assignee | ||
Comment 15•3 years ago
|
||
Assignee | ||
Comment 16•3 years ago
|
||
It seems that we've hit another instance of the XUL box model interacting poorly
with the HTML box model in mysterious ways. In this particular case, the <h2>
elements for subview subheaders was using the HTML box model while inside of
a tree of XUL box elements, and this was causing an incorrect height calculation
for the containing scrollable node, the panel-subview-body.
Switching the h2 element to use the XUL box model appears to fix this.
Updated•3 years ago
|
Comment 17•3 years ago
|
||
Comment 18•3 years ago
|
||
bugherder |
Comment 19•3 years ago
|
||
Can this one be uplifted to Beta 89 please?
Comment 20•3 years ago
|
||
Comment on attachment 9220420 [details]
Bug 1695617 - Make sure subview subheader elements use the XUL box model. r?Gijs!
Beta/Release Uplift Approval Request
- User impact if declined: MR1 / proton impact: useless scrollbar in some menus/panels
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: See comment 0
- List of other uplifts needed: nope
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): 1 line CSS change
- String changes made/needed: Nope
Updated•3 years ago
|
Comment 21•3 years ago
|
||
Comment on attachment 9220420 [details]
Bug 1695617 - Make sure subview subheader elements use the XUL box model. r?Gijs!
Low risk, approved for 89 beta 10, thanks.
Comment 22•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Reporter | ||
Comment 23•3 years ago
|
||
Verified - Fixed in latest Nightly 90.0a1 (2021-05-07) and Beta 89.0b10 (build id: 20210507073536), using Windows 10, Ubuntu 20.04 and macOS 11. The scrollbar is not displayed anymore in the toolbar library bookmarks and history panels. It is displayed only when the list of bookmarks or recent history is long enough to be scrollable.
Description
•