Closed
Bug 1847200
Opened 1 year ago
Closed 1 year ago
Don't create an internal event for transition events that we won't ever dispatch because of no listeners.
Categories
(Core :: CSS Transitions and Animations, task)
Core
CSS Transitions and Animations
Tracking
()
RESOLVED
FIXED
118 Branch
Tracking | Status | |
---|---|---|
firefox118 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sp3])
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•1 year ago
|
||
This rejiggers a bit the transition event setup to not carry around an
InternalTransitionEvent. We create one once we're ready to dispatch it.
We can implement similar optimizations for animation and playback
events.
Also moves the markers out of line because those constructors were
getting rather unwieldy.
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2d8142aa7fb1
Don't create an internal event for transition events that we won't ever dispatch. r=smaug
Comment 3•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
Updated•1 year ago
|
Whiteboard: [sp3]
Updated•1 year ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-516
You need to log in
before you can comment on or make changes to this bug.
Description
•