Open
Bug 1932917
Opened 2 months ago
Updated 2 months ago
composited transition discrepancies
Categories
(Core :: CSS Transitions and Animations, defect)
Tracking
()
NEW
People
(Reporter: kvndy, Unassigned)
Details
Attachments
(3 files)
Steps to reproduce:
Experiments related to https://bugzilla.mozilla.org/show_bug.cgi?id=1928801 using Firefox 132 on Ubuntu, using code similar to https://searchfox.org/mozilla-central/source/layout/style/test/test_transitions_replacement_on_busy_frame.html with artificial lag while (performance.now() - startTime < lag);
after changes. Unsatisfactory patches D229556 and D229614 for bug 1928801 were not applied.
Actual results:
- Compositor transition triggered on first mousedown does not start immediately and jumps when it does.
- Return transition after interrupt and retarget on second mousedown ends prematurely, with element jumping to final position.
- Return transition after interrupt and retarget on fourth mousedown jumps ahead after mouse move.
Expected results:
- First transition should start normally without a jump after the lag.
- Second transition should end normally without a jump at the end.
- Mouse move should not affect timing progress of fourth transition.
Reporter | ||
Comment 1•2 months ago
|
||
Reporter | ||
Comment 2•2 months ago
|
||
Chromium doesn't bother with adjusting start value to accomate for lag, resulting in a visual jump
Updated•2 months ago
|
Component: Untriaged → CSS Transitions and Animations
Product: Firefox → Core
Reporter | ||
Comment 3•2 months ago
|
||
Updated•2 months ago
|
Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in
before you can comment on or make changes to this bug.
Description
•