New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huge problem with onClick event on Buttons with chrome #7974
Comments
We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it. |
You made too many changes and plus there are less components in the beta, could you provide a workaround please to use chrome ? @oliviertassinari ps: your project is awesome, but I juste need one thing, the event.target.id with chrome on a button, the rest works perfectly |
@llllGEM Feel free to submit a PR to address the issue, we will review it. We are now focusing on the v1-beta branch. |
This works on V1. Just verify that you do gave a |
@slavab89 no it doesn't, here is my button Hello Mui ! when I click on the label inside the button I don't get the Id I must click inside the button outside the label for the handleclick method to get the id, which is very unpleasant and not a stable behavior, try it yourself on chrome, BTW I updated to beta9 and the issue is still there |
I see what you mean So based on the spec + stackoverflow it seems that button cant contain anything that's considered clickable and the recommendation is to use As an reference, |
@llllGEM Use |
@oliviertassinari thank you sir! I was having the same problem and that did the trick |
Problem description
Every event with onClick prop on every Button type (Raisedbutton or Flatbutton or Icon etc...)
I can't get the event.target.id or any other prop from the target as it is undefined, works perfectly on firefox but not on chrome, can you provide a workaround or a fix ?
toggleUpdate(event){ event.target.id //undefined}
Versions
The text was updated successfully, but these errors were encountered: