-
Notifications
You must be signed in to change notification settings - Fork 826
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
Tabs.Cleared
documentation a little ambiguous
#4241
Labels
Comments
Related to this,
This does raise the question: should there be this difference between |
The probably should be the same. |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
This was referenced Oct 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
Tabs.Cleared
message is documented as being "Sent when there are no active tabs. This can occur when Tabs are cleared, or if all tabs are hidden". This suggests thatTabs.cleared
or hiding every singleTab
are the only routes to causing this message to be posted.From what I can see simply setting
Tabs.active
to an empty string will cause this message to be posted too. The documentation should probably make it clear that this will also be a cause.A followup question, which might need to spin off into another issue, is: does it make sense that
Tabs.active
can be set (outwith of the workings ofTabs
) to an empty string? And if the answer is yes, the next question would be "why does doing this causeTabs
to behave as if the last-active-tab were still the active tab?"The text was updated successfully, but these errors were encountered: