-
Notifications
You must be signed in to change notification settings - Fork 47.4k
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
Bug: onTransitionStart #26065
Comments
It doesn't look like this bug report has enough info for one of us to reproduce it. Please provide a CodeSandbox (https://react.new), or a link to a repository on GitHub. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve |
When we do this, we should also add cancel and run for consistency. Seems like these weren't added because they didn't exist when that particular code was written. Not sure how much work is required to get this into the current synthetic event system. But then there are also plans to drop the synthetic event system at which point |
Should be easy to add to the list, I think. |
This has been supported by every major browser since March 2020. https://caniuse.com/mdn-api_element_transitionstart_event (Is this React thing still active?) |
React version: any
Steps To Reproduce
Add onTransitionStart and onTransitionEnd handlers to element with styles that contain transition declaration
Link to code:
react/packages/react-dom-bindings/src/events/DOMEventProperties.js
Line 119 in 0b4f443
Link to docs:
https://developer.mozilla.org/en-US/docs/Web/API/Element/transitionstart_event
The current behavior
onTransitionEnd fires, onTransitionStart doesn't
The expected behavior
Both handlers should fire
The text was updated successfully, but these errors were encountered: