I haven’t tested in isolation but I’ve observing that after a domain reload I use the assembly callback to repaint the UI which loads a UXML template and does SetEnabled(false) on a Button when some functions are called during use.
This works fine until I do a domain reload, then it gets weird.
What i’m seeing is the button’s enabledSelf state evaluating correct, but the Button is turned to an active state and handles interaction/events as if it were active. I have to call this in the OnGUI state to set it correctly since there’s no apparent way to see if it’s truly enabled - since enabledSelf actually is correct.
Has anyone experienced this? I’m going to make a smaller repro case and send a bug report if I can reproduce consistently but was curious if anyone else has this experience with SetEnabled.