HelpPanel shows the wrong widget's help if focus moved while the app was blurred or a modal was open
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start with HelpPanel.update_help, which returns early while the app is blurred or its screen is inactive, and see how Screen.bindings_updated_signal is published from App._on_app_focus, App._on_app_blur and _watch_stack_updates. Run the issue's two reproduction scripts, blur_case and modal_case. Done when the panel shows the help of the widget focused after AppFocus or after a modal is popped, and the existing help panel tests still pass.
Written by the indexing model from the issue text.
Description
Hi! I hit this while writing generated tests against Textual's widgets.
HelpPanel.update_help returns early while the app doesn't have focus, or while its screen isn't the active one. That makes sense, but nothing runs it again when the app gets focus back or the screen is resumed. So if focus moves in the meantime, the panel keeps the help of the widget that was focused before.
Two ways to see it:
- The terminal loses focus (
AppBlur), the app moves focus (a timer, a worker, a message), then the terminal gets focus back (AppFocus). - Focus moves on a screen while a modal covers it, then the modal is popped.
import asyncio
import textual
from textual import events
from textual.app import App, ComposeResult
from textual.screen import ModalScreen
from textual.widgets import Button, HelpPanel, Input, Markdown
class First(Input):
HELP = "Help for the **first** input."
class Second(Input):
HELP = "Help for the **second** input."
class Modal(ModalScreen):
def compose(self) -> ComposeResult:
yield Button("OK")
class HelpApp(App):
def compose(self) -> ComposeResult:
yield First(id="first")
yield Second(id="second")
def on_mount(self) -> None:
self.action_show_help_panel()
def shown_help(app: App) -> str:
return app.screen.query_one(HelpPanel).query_one(Markdown).source
async def blur_case() -> None:
app = HelpApp()
async with app.run_test() as pilot:
await pilot.pause()
app.query_one("#first").focus()
await pilot.pause()
print("focused first: ", repr(shown_help(app)))
# The terminal loses focus, the app moves focus, the terminal gets focus back.
app.post_message(events.AppBlur())
await pilot.pause()
app.query_one("#second").focus()
await pilot.pause()
app.post_message(events.AppFocus())
await pilot.pause()
print("after refocus: ", app.focused.id, repr(shown_help(app)))
async def modal_case() -> None:
app = HelpApp()
async with app.run_test() as pilot:
await pilot.pause()
app.query_one("#first").focus()
await pilot.pause()
base = app.screen
app.push_screen(Modal())
await pilot.pause()
# Focus moves on the base screen while the modal covers it.
base.set_focus(base.query_one("#second"))
await pilot.pause()
app.pop_screen()
await pilot.pause()
print("after pop: ", app.focused.id, repr(shown_help(app)))
print("Textual", textual.__version__)
asyncio.run(blur_case())
asyncio.run(modal_case())
Output on Textual 8.2.7 (main at 5e5b7ef is the same):
Textual 8.2.7
focused first: 'Help for the **first** input.'
after refocus: second 'Help for the **first** input.'
after pop: second 'Help for the **first** input.'
Expected: once the app has focus again, or the screen is resumed, the panel shows the help for the widget that is focused then (Help for the **second** input.).
KeyPanel and Footer don't have this problem, because they update from Screen.bindings_updated_signal. That signal is published on AppFocus and AppBlur (App._on_app_focus / _on_app_blur call refresh_bindings) and when a screen is resumed (_watch_stack_updates). I think HelpPanel could listen to it too, and catch up there. I'm happy to send a PR.
- Dominant language
- Python
- Stars
- 37.7k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Textualize/textual
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Textualize/textual#6790 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Textualize/textual#6789 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Textualize/textual#6787 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Textualize/textual#6782 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Textualize/textual#6778 · 1 comment ·
All issues in Textualize/textual
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
GoogleCloudPlatform/professional-services-data-validator#1899 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day