I'm seeing behavior in the next/Button widget where disabled buttons are still calling onClick. The buttons appear visually disabled. Occurs in the simplest case:
<Button onClick={() => console.log('just got clicked')} disabled>Click Me</Button>
Thanks for the report. I'm on it 馃憤 .
onTouchTap still invoke when disabled
<Button
raised
disabled={!this.state.email}
color='primary'
className={classes.button}
onTouchTap={this.getCode}
>
Get Verification Code
</Button>
@ng-hai onTouchTap is no longer supported.
Is it OK if I remove react-tap-event-plugin when using v1-alpha version?
@ng-hai Yes, you should.
What is the alternative of onClick and onTouchTap?
Because typescript throw error "'IntrinsicAttributes & ButtonProps & { children?: ReactNode; }'."
@oliviertassinari Is there a handler still fired even when the button is disabled? I want to add handling to highlight missing fields on a form.
Most helpful comment
@ng-hai Yes, you should.