Closed
Bug 582384
Opened 14 years ago
Closed 14 years ago
When hovering over some corners of elem with transform & non-transform transitions, the non-transform completes but transform does not
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
DUPLICATE
of bug 582379
People
(Reporter: dholbert, Unassigned)
References
()
Details
Attachments
(2 files)
STEPS TO REPRODUCE: 1. Load URL or testcase. 2. Move cursor to absolute lower-right corner of the div (point 'b' in testcase) EXPECTED RESULTS: Transform & color transitions should "jitter" back and forth between intermediate states, as the div enters & leaves 'hover' status. ACTUAL RESULTS: The transform transition jitters, as expected, but the color transitions complete, arriving at the final values (white text on red background). There's usually a little bit of "jitter" with the color values, but they tend to get past that pretty quickly and stabilize on the final value.
Reporter | ||
Comment 1•14 years ago
|
||
I'm testing with today's linux x86_64 nightly, btw: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b3pre) Gecko/20100727 Minefield/4.0b3pre
Reporter | ||
Comment 2•14 years ago
|
||
This testcase also has a 'font-size' transition, which matches the behavior of 'color', completing its transition. NOTE: I can get closer to (or even reach?) the EXPECTED RESULTS if I position my cursor a little ways to the left of the 'b' character, in both testcases attached so far. However, if I position my cursor *on* the 'b' character (its resting position), I always get ACTUAL RESULTS.
Reporter | ||
Updated•14 years ago
|
Summary: When hovering over some corners of elem with transform/color transitions, the color transition completes but transform transition does not → When hovering over some corners of elem with transform & non-transform transitions, the non-transform completes but transform does not
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•