[Affected versions]: - 64.0b5 - 63.0 - 65.0a1 [Affected platforms]: - macOS 10.13.6 - Mac OS X 10.10.5 [Steps to reproduce]: 1. Launch Firefox 2. Enable the bookmarks toolbar 3. Add some separators (by using the "New Separator" context menu option) 4. Move the separators anywhere in the bookmark toolbar. [Expected result]: - The separators can easily be selected and moved anywhere in the toolbar. [Actual result]: - The separators are extremely difficult to select and thus, the browser itself ends up moving with the cursor. [Regression range]: - Will return with regression range ASAP.
Component: Widget: Cocoa → General
Product: Core → Firefox
Hello, I have returned with a regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4403805b3b66f4a130f21d0d2ae036b8fc9d6f5b&tochange=e43f2f6ea111c2d059d95fa9a71516b869a69698 Hope it helps.
(In reply to Vlad Lucaci (:vlucaci) from comment #0) > Created attachment 9021187 [details] > Verical separators hard to select This video doesn't seem to be publicly viewable. The regression window is quite broad. Is it possible to narrow it down further? Moving to Bookmarks/History for now, but it's possible the regression is somewhere else... it's hard to tell from that window, as I don't see obvious suspects in theme/bookmarks/gfx code.
Component: General → Bookmarks & History
Hello Gijs, I will try to narrow down the regression range a little bit more . In the meantime I won't clear the needinfo request. Here is the video attachment again: https://drive.google.com/file/d/1L0BwlDJvjGYATL-jeKwYtMsF7L_gj1U2/view?usp=sharing
Priority: -- → P3
Hello guys, I tried to get a more narrowed regression range for this issue multiple times, and everytime got to the builds from 2016 ,with the same outcome. It seems that the separators were difficult to select ever since then. So I believe that this issue is actually not a regression.
Marking fix-optional for 65 and 66 so that these already triaged issues don't show up repeatedly in weekly regression triage. Happy to take a patch in nightly.
You need to log in before you can comment on or make changes to this bug.