Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bookmark folder popup position not always ideal #1155

Open
maxmilton opened this issue Jul 12, 2021 · 5 comments
Open

Bookmark folder popup position not always ideal #1155

maxmilton opened this issue Jul 12, 2021 · 5 comments
Labels
bug Something isn't working UX
Milestone

Comments

@maxmilton
Copy link
Owner

maxmilton commented Jul 12, 2021

Now that #1151 is merged we have bookmark folder popup position that is "good enough" for general use but the experience is not ideal in all scenarios.

For context, "top level" means a folder is on the bookmark bar itself and not nested inside another folder.

Folder popup position scenarios

  1. Normal/default position
    • Top level: Show below the parent
    • Nested: Show beside the parent (on the right side)
  2. Overflowing viewport to the right
    • Top level: Align the popup to the right edge of the viewport
    • Nested: Show beside the parent (on the left side)
      • Subsequent nested folder popups should also open to the left
        • At this point if a popup overflows to the left of the viewport then open to the right of the parent
  3. Overflowing viewport both left and right
    • If the viewport is very narrow and the popup overflows on both sides there's basically nothing we can do. In this case the user will need to use the native bookmark bar or bookmark manager.

The current popup position logic from #1151 covers everything other than opening subsequent nested folder popups to the left (and then to the right if overflowing the left edge of the viewport).

Other issues

  • Popups remain in place when the parent is scrolled. Native chrome closes the popup upon scrolling the parent, perhaps we should do the same. TBH it's not such a big deal though.
@maxmilton maxmilton added the UX label Jul 12, 2021
@maxmilton maxmilton added this to the v1.0.0 milestone Jul 12, 2021
@maxmilton maxmilton added the bug Something isn't working label Oct 24, 2021
@dror-g
Copy link

dror-g commented Jun 10, 2022

I'll add that popups open beside the selected item, and if it's a folder near the bottom of the screen - there's no space to display its contents.
Getting a scroller with just one line visible.

@guest271314
Copy link

We can now access Bookmarks using side panel on any page so this shouldn't be an issue any more.

@maxmilton
Copy link
Owner Author

@guest271314 it's more about having immediate access to the bookmarks on the new tab page and hiding bookmarks elsewhere. In the same vane the native bookmarks bar is available any time, however, there's no way to show and hide it programmatically.

Additionally, I've come to really enjoy this extension's bookmark bar implementation which shows folder on hover. It's really fast and convenient to access bookmarks.

That said, the UI still needs a lot of work. I've been following along with progress on the CSS anchor positioning API and the popover API as potential solutions to reduce the amount of code required compared to all the positioning JS needed.

Refactoring the UI and combustibility are things I'd definitely like to get to soon.

@guest271314
Copy link

We can programmatically open the side panel, and provide any content we want there, besides the default list that includes the Bookmarks, here on the extension defined new tab page that I use

Screenshot_2023-12-25_12-55-09

We can certainly create an element that is displayed the same window positioning as the native Chromium UI bookmarks panel.

Maybe I'm not getting what you are describing.

@guest271314
Copy link

E.g.,
Screenshot_2023-12-25_13-16-59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working UX
Projects
None yet
Development

No branches or pull requests

3 participants