-
Notifications
You must be signed in to change notification settings - Fork 827
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
Scrolling no longer works in 0.6.0 and 0.7.0 #1388
Comments
Just detected another difference between 0.6.0 and 0.7.0: In 0.6.0 key press on a focused input had a higher priority than key bindings on a Screen. In 0.7.0 a Screen binding has a higher priority. This leads to the following scenario:
Just tell me, if should open a separate issue with a running example. At first, it looks related. |
That would be expected as it was decided that |
The priority bindings should really be used for things like hot-keys only, think ctrl+C which you don't want to be consumed by an Input. We need to rethink how bindings are handled. @mitosch we're aware of the problem. Leave it with us. |
Thanks. Feel free to close the issue or change the title. |
Retested: Fixed in 0.8.0. |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
Maybe related to #1343
In 0.6.0 and 0.7.0 the scrolling with up, down, page up, page down seams to work different (or not as expected).
Steps to reproduce:
python -m textual
In 0.6.0, 0.7.0 and main the screen does not move.
I've read the changes about
PRIORITY_BINDINGS
and tried to use it in my app, where I have a long list in a container with items (Item(Static, can_focus=True)
) which used to behave the same as the demo. I tried to applyPRIORITY_BINDINGS
to App, Screen and other Containers which should receive the scrolling actions without any luck.As the demo behaves the same as my app, it could be a bug. Or am I missing something and a fix could be easy.
Thanks for any assistance.
The text was updated successfully, but these errors were encountered: