Open Bug 1855226 Opened 2 years ago Updated 11 months ago

Regression: (Usually) can't drag scrollbar in "Show all the bookmarks folders" in bookmarking pane

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 117
Desktop
Linux
defect

Tracking

()

Tracking Status
firefox118 --- affected
firefox119 --- affected
firefox120 --- affected

People

(Reporter: from_bugzilla3, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

  1. Click the bookmarking star
  2. Click the "Show all the bookmarks folders" button
  3. Attempt to drag the handle on the tree view's scrollbar

Actual results:

Usually (it sometimes temporarily works after a browser restart), nothing... as if I I hadn't pressed the left mouse button at all.

Expected results:

Up until maybe 6 to 12 months ago (I'm terrible with time), it'd just work.

Now, I have to rely on my scroll wheel and the keyboard to scroll the widget.

(Yeah. This is another one of those bugs where I was wasn't in a mindstate where I couldn't bring myself to accept the possibility of being asked to test without extensions when, AFAIK, WebExtensions doesn't give a means for extensions to meddle there... especially given that this is something that may take time after the browser starts up, and I refuse to browse the web without privacy extensions, so I'd be committing to wasting time on a pointless busywork to exercise the test profile on LAN devices I have no reason to be poking at with no solid estimate for how much time I need to spend doing so before I can consider the question of "does it occur..." answered.)

The Bugbug bot thinks this bug should belong to the 'Firefox::Bookmarks & History' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Bookmarks & History

Managed to reproduce this issue on my end but I also confirm that it's intermittent. I tried on Ubuntu 20.04 x64.
Since the issue is intermittent I couldn't find a regression range.

Severity: -- → S4
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
OS: Unspecified → Linux
Hardware: Unspecified → Desktop

We've only heard reports about this on Linux, so tentatively moving across to that component.

Does this occur for any other pop-ups or windows?

Component: Bookmarks & History → Widget: Gtk
Product: Firefox → Core
Priority: -- → P3

Confirming this appears on Windows as well (Windows 11 24H2, Firefox 143.0.1). I have a suspicion the issue is related to display scaling. The problem only occurs on my primary display, which is 3840x2160 with 150% scaling. I have three other external displays which are all 1920x1200 with 100% scaling and the issue doesn't occur on any of them.

I have a suspicion the issue is related to display scaling.

I think you're on the right track there.

My displays aren't "scaled", per se (all 100%), but my central monitor has noticeably smaller pixels than my wing monitors (1920x1080 @ 21.5" vs. 1280x1024 @ 19") and whether the tree view's scrollbar works for a bookmarking popup from this window depends on which monitor it's on. (If I put it on the central monitor, it works. If I put it on one of the wing monitors, it doesn't... I just can't rule out other factors like the central monitor being the primary display.)

Here's the relevant dimensional info:

% xrandr
Screen 0: minimum 8 x 8, current 4480 x 1080, maximum 32767 x 32767
HDMI-0 connected 1280x1024+3200+0 (normal left inverted right x axis y axis) 376mm x 301mm
   1280x1024     60.02*+  75.02  
[...]
DP-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
   1280x1024     60.02*+  76.00    75.02    72.00  
[...]
DP-3 connected primary 1920x1080+1280+0 (normal left inverted right x axis y axis) 479mm x 269mm
   1920x1080     60.00*+
[...]

...and, In case it's relevant, this has been in my ~/.Xresources for about a decade:

! Fix font-size idiocy related to my having multiple monitors with mixed DPI
Xft.dpi: 96
You need to log in before you can comment on or make changes to this bug.