New Library info pane overlaps the list of bookmarks
Categories
(Firefox :: Bookmarks & History, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr91 | --- | wontfix |
firefox61 | --- | unaffected |
firefox62 | --- | wontfix |
firefox95 | --- | wontfix |
firefox96 | --- | wontfix |
firefox97 | --- | wontfix |
firefox99 | --- | wontfix |
firefox100 | --- | wontfix |
firefox101 | --- | verified |
People
(Reporter: gingerbread_man, Assigned: jteow, Mentored)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fxsearch][lang=js])
Attachments
(2 files)
Reporter | ||
Updated•7 years ago
|
Comment 1•7 years ago
|
||
Updated•7 years ago
|
Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Comment 4•7 years ago
|
||
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Comment 7•7 years ago
|
||
Updated•7 years ago
|
Comment 9•6 years ago
|
||
Updated•6 years ago
|
Comment 11•6 years ago
|
||
The general thoughts for fixing this are:
- Having the Library window revert to horizontal alignment of fields would be acceptable.
- It would possibly be best to separate the styles of the library window and the Star UI panels but we're not sure how easy that will be.
So if we can un-share we could then revert the changes in bug 1459885 for just the library window.
Comment 13•5 years ago
|
||
Any update on fixing this issue? As Mark Banner said, reverting changes in bug 1459885 for just library window looks appropriate and easy fix (at least from user perspective ;) ).
It's kinda extremely annoying to manage bookmark folder with bookmarks exceeding visible area (please see attachment from duped bug #1477541 - https://bug1477541.bmoattachments.org/attachment.cgi?id=8994005 ).
Updated•5 years ago
|
Comment 14•5 years ago
|
||
Mark said we can revert changes if we can unshare, that's unlikely for now.
I said what I think we should do in comment 1.
Updated•5 years ago
|
Comment 15•5 years ago
|
||
(In reply to Marco Bonardo [:mak] from comment #1)
[...] Anyway we should first fix Bug 1468992
It's fixed for over 1 year.
(In reply to Marco Bonardo [:mak] from comment #1)
and then we can decide to either
make the panel a fixed height, so it doesn't flicker, or scroll the tree so
the selected item is always visible after updating the pane.
I support unchanged, permanent and constant height of panel, as you said, no annoying flickering, so I'm choosing gate... err ...option number 1. ;)
Comment 16•5 years ago
|
||
it's not matter of choosing an option, it's matter of making a patch.
Comment hidden (advocacy) |
Comment 20•4 years ago
|
||
After initializing the pane, we should ensure the selected item, if present, is scrolled into view. The treeview has an ensureRowIsVisible method that could be used. the code for the library lives in https://searchfox.org/mozilla-central/source/browser/components/places/content/places.js
Comment 23•4 years ago
|
||
I hope this is appropriate.
The reason the link does not open is because it is not under the finger for the 2nd part of the click event. It moves up and the finger now points to the next in line link.
Seems to me the best solution would be to increase the bottom section to prevent the link(s) from moving when the bottom is selected.
Any change in the link list will cause the user to be on a wrong link for the complete click event.
Comment 24•4 years ago
|
||
a potential solution in comment 20, but it should be tested.
Comment 25•4 years ago
|
||
Hello Marco,
I am trying to work on this bug, in accordance with your suggestion on comment 20
Thanks
Comment 26•4 years ago
|
||
If you move the selected link into view wouldn't that possibly make the pointer NOT be pointing to the desired link?
Resizing the window would keep the bottom of the view in the same place therefore the pointer would stay on the desired link.
Comment 27•4 years ago
|
||
Resizing the details pane has other downsides, it would take up major space while being mostly empty on non-uris. I'm not sure there's a win-win solution here, and the Library is in low-maintenance mode, because we'd really like to move it into something newer in-content, where we'd also have more available space for its contents.
You're right that the right and middle click operations should work on the appropriate element, not on the panel, and the fix should ensure those work, even with an automated test. If that becomes too complicate we're open to evaluate alternative approaches.
(feel free to work on this, of course).
Comment 28•4 years ago
|
||
There are 4 rows used for the title of the field. Could the name (Name, URL, Tags, Keyword) be moved to the same line/row as the text field? That may be sufficient. It sure is a nuisance the way it is. I have too many bookmarks.
Sorry I don't have the talent to work on this bug. :)
Reporter | ||
Updated•4 years ago
|
Comment 29•4 years ago
|
||
After digging a bit I found that my suggestion was possibly a change in the other directions.
https://bugzilla.mozilla.org/show_bug.cgi?id=1459885
===
Dão Gottwald [::dao]
Assignee
Description • 4 years ago
Instead of:
Name: []
Folder: [][v]
Tags: [_______][v]
the new layout looks like this:
Name:
[_____________]
Folder:
[__________][v]
Tags:
[__________][v]
Comment 30•4 years ago
|
||
We can't change the UI without specific approval from UX, and at the moment that team is extremely busy, so we must fix it in code if we want this to proceed sooner.
Comment 31•4 years ago
|
||
Set release status flags based on info from the regressing bug 1459885
Updated•4 years ago
|
Comment 32•4 years ago
|
||
Set release status flags based on info from the regressing bug 1459885
![]() |
||
Comment 33•4 years ago
|
||
FWIW I have been using userchrome.css
to hide the keyword field as a partial workaround ever since the "More/Less" toggle was removed, but things seem to have gotten worse after migrating from ESR78. Two extra lines of description, Use tags to organize and search for bookmarks from the address bar
and Use a single keyword to open bookmarks directly from the address bar
were added to the library infopane. I had originally assumed these would only persist during some onboarding grace period but alas.
Updated•4 years ago
|
Assignee | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Comment 34•3 years ago
|
||
Comment 35•3 years ago
|
||
Comment 36•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Updated•3 years ago
|
I managed to reproduce this bug on Firefox 100.0(20220428192727) on macOS 11. Confirmed as fixed on Firefox 101.0b4(20220508185621) and Nightly 102.0a1(20220509190429) on macOS, Ubuntu 20.04 and Win10-64 bits.
Comment 38•3 years ago
|
||
We're backing out the fix that landed here in bug 1786518 due to annoying regressions it caused, we'll instead look into a UI solution like bug 1786322 that should remove risk of more edge cases
Description
•