From d6c19e03b8f6ce6046a13bea5c15e4ccbb8b3fc9 Mon Sep 17 00:00:00 2001 From: cloud Date: Wed, 17 Jun 2026 23:53:05 +0200 Subject: [PATCH] fix: action lookup stops when matching action has isEnabled set to false --- .../src/content/ui/interactivity/actions-and-shortcuts.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/sites/docs/src/content/ui/interactivity/actions-and-shortcuts.md b/sites/docs/src/content/ui/interactivity/actions-and-shortcuts.md index 790ed9d75fa..0ce246fe25b 100644 --- a/sites/docs/src/content/ui/interactivity/actions-and-shortcuts.md +++ b/sites/docs/src/content/ui/interactivity/actions-and-shortcuts.md @@ -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. The previous example uses a `Builder` because `Actions.handler` and `Actions.invoke` (for example) only finds actions in the provided `context`, and