Closed willmcgugan closed 1 month ago
As mentioned, maybe this should be union of true/false/none. The value at App takes precedence. If the value is set (not None) at the Screen level, the the value from the Screen overrides.
It could be done with a binding. But it would place a burden on the dev not to break it, and to do the right thing if they want to bind escape for something else. Maybe we could add something to the binding system to make that a non-issue in the future, but I don't know what that would look like.
Fixes https://github.com/Textualize/textual/issues/4949