-
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
A Widget
-derived widget with inherit_bindings=False
, but no BINDINGS
, appears to still inherit bindings
#1351
Comments
Much the same issue as #1336 |
@davep I'll be happy to tackle this one. |
Yup. Suspect that will do it. |
davep
added a commit
to davep/textual
that referenced
this issue
Dec 13, 2022
davep
added a commit
to davep/textual
that referenced
this issue
Dec 13, 2022
Testing the overlap between Textualize#1343 and Textualize#1351.
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
davep
added a commit
to davep/textual
that referenced
this issue
Dec 13, 2022
This now is fine thanks to Textualize#1352 fixing Textualize#1351.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is very much related to #1343, but I think merits an issue of its own to consider first. The reasons why this happens seem clear enough, but I feel the setup may cause confusion. With Textual as it is of 0.6.0 (with the bindings for movement keys being on
Widget
), consider this widget:vs this:
In the former case the bindings of
Widget
are still inherited. In the latter they're not.The text was updated successfully, but these errors were encountered: