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

Update Theme: Sidebery #990

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update Theme: Sidebery #990

wants to merge 2 commits into from

Conversation

L-Acacia
Copy link

@L-Acacia L-Acacia commented Feb 2, 2025

The extension wasn't hiding the tab-bar when the setting was turned on newer zen versions.
It also was hiding the theme picker by moving it outside of the window with the sidebar.
The opacity is set to 0 since some SVG where still showing without it.

@kolemcrae
Copy link

Any way I can vote to get this reviewed sooner? I want my sidebery working!

@Dathuss
Copy link

Dathuss commented Feb 12, 2025

Wowie that actually worked, thanks a lot ! that was the only thing keeping me from updating to the newer versions.

@donaldguy
Copy link

donaldguy commented Feb 17, 2025

A little off topic but of obvious interest:

On a functionality level, 1.8t (current Zen Twilight; also back a few days [1.7.7t]) does not get along very well with sidebery:

  • a lot tabs disappearing and/or showing up under the wrong panel - empty/homepage tabs proliferating unhelpfully instead.
  • [at least this is my experience with trying to use container rules to map across between tab panels and workspaces, and using both UIs - in a way that mostly1 works in current stable (1.7.6b);

    can't speak to just trying to be a sidebery purest]

I imagine this is related to what has been written in the changelog as:

Tabs are handled in different containers, meaning faster transitions and better swiping experience

but I haven't chased it down to actual PRs/commits to see what that means in practice (and determine whether its workaround-able)

This seems to be the case with both:

  • {(shanto/Sidebery)/"Sidebery (Zen)"} -which is 5 months back + the CSS to do e.g. transparency–and
  • with upstream Sidebery (@ 5.3.2)

Footnotes

  1. modulo Zen tabs sometimes showing tabs from multiple workspaces if I switched between containers using sidebery panels; and "Hide native tabs in folded branches" not surviving workspace changes (but I'm honestly mostly surprised it works at all)

@L-Acacia
Copy link
Author

L-Acacia commented Feb 19, 2025

@donaldguy If you plan on using sidebery, I feel like you should avoid zen features related to tab management.
Most those Zen features have a sidebery equivalent, and even if they integrate worse in the browser, you'll have a more stable experience.

I personally only use one zen workspace, with no default container, no tab unloading, and pin stuff only in sidebery. Then handle all of that with sidebery. The experience has been perfect (except for glances which do work but slightly less smoothly).
I also recommend using the autosnapshot tool of sidebery in case the extension and the browser start to conflict at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants