Open MaximBalaganskiy opened 3 years ago
@patrickrodee , could you verify whether this is intended?
This is a bug. The fix is to type the animationend
and transitionend
handlers in the component (following the existing handlers), then define the handlers in initialSyncWithDOM
, listen for the appropriate events ("animationend"
for handleAnimationEnd
, "transitionend"
for handleTransitionEnd
), and unlisten when the component is destroyed. Tests would then need to be updated to ensure the handlers are correctly setup and correctly torn down.
This should be reasonable to contribute if anyone wants to.
Bug report
Chip
component does not callfoundation.handleAnimationEnd
Your Environment: