Open
Bug 731886
Opened 12 years ago
Updated 2 years ago
Transitions to/from 'auto' & intrinsic widths (e.g. -moz-max-content) don't work
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: dholbert, Unassigned)
Details
Attachments
(1 file)
|
989 bytes,
text/html
|
Details |
When a transition-enabled length changes to an intrinsic width keyword like "-moz-max-content", the transition doesn't take place.
STR:
1. Load testcase
2. Hover divs
EXPECTED RESULTS:
All divs transition their widths gradually when hovered.
ACTUAL RESULTS:
Only the green div ("width: 200px") transitions its width gradually -- the other two just snap to the new width.
|
Reporter | |
Comment 1•12 years ago
|
||
FWIW, the testcase includes webkit transition & intrinsic keywords, for comparison. Webkit does perform a smooth transition, but they jump to "0" as the transition start-point instead of starting at the actual resolved value of the keyword. (Testing w/ Chromium 17.0.963.56)
|
|
Reporter | |
Updated•12 years ago
|
OS: Linux → All
Hardware: x86_64 → All
|
|
Reporter | |
Updated•12 years ago
|
Summary: Transitions to/from 'auto' & intrinsic widths (-moz-max-content) don't work → Transitions to/from 'auto' & intrinsic widths (e.g. -moz-max-content) don't work
|
||
Comment 2•12 years ago
|
||
Note discussion in bug 660791 about this exact issue for "auto".
|
||
Comment 3•11 years ago
|
||
Seems like a duplicate of bug 571344.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•