Skip to content

fix: action lookup stops when matching action has isEnabled set to false #13516

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.

Sign up for GitHub

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

Open
pathconnected wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: action lookup stops when matching action has isEnabled set to false #13516

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions sites/docs/src/content/ui/interactivity/actions-and-shortcuts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -321,9 +321,8 @@ Widget build(BuildContext context) {

The `Actions` widget only invokes actions when `isEnabled(Intent intent)`
returns true, allowing the action to decide if the dispatcher should consider it
for invocation. If the action isn't enabled, then the `Actions` widget gives
another enabled action higher in the widget hierarchy (if it exists) a chance to
execute.
for invocation. If the action isn't enabled, the action is not invoked and the
framework stops searching for matching actions at that point.
Comment on lines +324 to +325

@gemini-code-assist gemini-code-assist Bot Jun 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To adhere to the semantic line breaks guidelines, each sentence should start on a new line. Please split the sentence starting with "If the action isn't enabled..." onto its own line.

Suggested change
for invocation. If the action isn't enabled, the action is not invoked and the
framework stops searching for matching actions at that point.
for invocation.
If the action isn't enabled, the action is not invoked and the
framework stops searching for matching actions at that point.


The previous example uses a `Builder` because `Actions.handler` and
`Actions.invoke` (for example) only finds actions in the provided `context`, and
Expand Down
Loading