Skip to content

Fix disabled button consumes input#338

Open
SalavatR wants to merge 1 commit intoInsality:masterfrom
SalavatR:disabled_button_fix
Open

Fix disabled button consumes input#338
SalavatR wants to merge 1 commit intoInsality:masterfrom
SalavatR:disabled_button_fix

Conversation

@SalavatR
Copy link
Copy Markdown
Contributor

@SalavatR SalavatR commented Apr 16, 2026

Hi!
We noticed that when two buttons are stacked one above another, a disabled button still consumes input. To ensure correct behavior, we now use the following code:

self.button:set_enabled(enabled)
self.button:set_input_enabled(enabled)

@Insality
Copy link
Copy Markdown
Owner

Hello! Looking into this

The disabled button with set_enabled(false) should consume input, since it have a behaviour for disabled animations and callbacks in styles and some of users using this afaik. Maybe bad naming but it is

I think the correct way is to disable input of that component as you do. Just not consuming disabled input will introduce breaking changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants