Do you have an example of it not working? We are using material ui in our appliance and I haven't experienced problems with event handlers not firing.

[Tabs {:on-change #(.log js/console "never called") :value 0} 
  [Tab {:label "first"}] 
  [Tab {:label "second"}]]

the on-change (or onChange spelling doesn’t matter) is simply never called… on-change in textfield inputs works fine

same goes for non-native Select (doesn’t fire on-change events)

ok, our wrapper had an extra layer of components there, which caused mui to not be able to pass the on-change to children

changing [Tab ...] to (Tab ...) works

I've struggled with some issues regarding wrapping material-ui components with my own components (last time i tried was with RadioGroup). I tend to not do this unless it is absolutely necessary because of the way that material-ui handles child state derived from parent state. I think in your situation though, if you didn't want to do the function call, you can pass an :on-click to each Tab.

[Tabs {:value @tab-value}
  [Tab {:label "first" :on-click handler}]
  ...]

I don't know if you've solved this or not yet but what are you using a key for that element?

just tried with:

[:input {:key "testemail"
                :type "email"
                :value ($sub [::test])
                :on-change ($evt [::test])}]