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

Request | A third option for "After closing parent tab" pls? #779

Closed
guigirl42 opened this issue Sep 29, 2022 · 9 comments
Closed

Request | A third option for "After closing parent tab" pls? #779

guigirl42 opened this issue Sep 29, 2022 · 9 comments

Comments

@guigirl42
Copy link

Description

This is in my current installed 5.0.0b27. Note the yellow highlight marking the present two options when we close the parent-tab of a tab-tree:

image

This is the approximately comparable settings' section from TreeStyleTab; note my green highlight:

image

I love using Sidebery, i think it's amazingly good ... but this specific function/option for my comfortable daily use-case is much better in TST than Sidebery.

Would it be possible please to provide this additional option in Sidebery, when closing the parent-tab of an existing tree that still has child-tabs?

@guigirl42 guigirl42 changed the title A third option for "After closing parent tab" pls? Request | A third option for "After closing parent tab" pls? Sep 29, 2022
@guigirl42
Copy link
Author

Hello. Any thoughts on this possibility pls?

@mbnuqw mbnuqw closed this as completed in d85c230 Feb 25, 2024
@mbnuqw
Copy link
Owner

mbnuqw commented Feb 25, 2024

Implemented, but only for closing the parent tab. Handling a moved parent tab is quite tricky and therefore wontfix.

@guigirl42
Copy link
Author

Oh, i don't think i understand, but i look forward to being able to test it soon so i can properly see what you mean. Presumably in v5.1.1.8 ?

@guigirl42
Copy link
Author

Now i do have v5.1.1.8, & have tested it. It works just as i'd hoped. Excellent, Max, many thanks! 🤗

@guigirl42
Copy link
Author

Oh actually, i've found a little detail that differs from the way this works in TST, & it's better in TST.

In TST, once this temporary / dummy parent placeholder is created after the original parent is closed, & the user progressively reads then closes each of its child tabs, once the final child is closed, that dummy parent placeholder is automatically closed as well, which is nice.

In Sidebery, with this new feature, closing the final child does not automatically close the dummy parent placeholder, so the user then needs to manually close it.

Would it be possible pls to tweak your nice new feature so that once the final child is closed, that dummy parent placeholder is automatically closed as well? Thanks.

@mbnuqw
Copy link
Owner

mbnuqw commented Feb 28, 2024

It's a different, planned feature - Automatically close empty group pages. And I literally yesterday considered implementing it - but I didn't find any issues requesting it and also didn't find it useful for myself, so I decided to postpone this feature. Well, at least now I know that there is a request. I'll move it up in my task list.

@guigirl42
Copy link
Author

This morning i got v5.1.1.9. I eagerly went to the Release Notes to see what new goodies it might have, but only saw the identical msg as happened for 5.1.1.8, 5.1.1.7, & 5.1.1.6, viz:

Empty release to re-upload incorrectly uploaded version on AMO

I don't understand what this means.

@mbnuqw
Copy link
Owner

mbnuqw commented Mar 4, 2024

Nightly builds are automated (although triggered by me) releases, that are appended to the last stable (v5.1.1 in this case) release. Just like the Firefox Nightly I don't plan to write release notes for each, since it's time-consuming. There are Changelog with "unreleased" section which I update a couple of times a week and commits. After the v5.2.0, which is almost there, I also plan to use Github milestones (or Github projects) so you will be able to see planned features for the next stable release.

@guigirl42
Copy link
Author

Thank you.

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

No branches or pull requests

2 participants