Closed
Bug 1510921
Opened 6 years ago
Closed 5 years ago
CSS transition-timing-function no longer has frames(); steps() enhanced
Categories
(Developer Documentation Graveyard :: General, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: tshinnic, Unassigned)
References
()
Details
:: Developer Documentation Request Request Type: Correction Gecko Version: unspecified Technical Contact: :: Details It is hard to know what combination of current standards docs defines all aspects of CSS transition-timing-function, with at least "CSS Animations Level 1" (https://www.w3.org/TR/css-animations-1/) and "CSS Easing Functions Level 1" (https://www.w3.org/TR/css-easing-1/) pertinent. However it is certainly true that no *current* spec version mentions the "frames()" function documented in this MDN page. I finally found mention at https://www.w3.org/TR/2018/WD-css-easing-1-20181009/#changes that The following changes have been made since the 21 February 2017 Working Draft: Removed `frames()` timing function. Added jump-start, jump-end, jump-none, and jump-both keywords to steps() timing function. That earlier spec version does mention the frames() function at https://www.w3.org/TR/2017/WD-css-timing-1-20170221/#frames-timing-functions It appears that the proposed usages of frames() were replaced by elaboration of steps() as noted above, and indeed the MDN page does not yet mention those added keywords (e.g. "jump-start") Please delete frames() from the MDN page, and elaborate the description for steps() with the new enhancements and keywords. Note: the current spec "CSS Easing Functions Level 1" was previously named "CSS Timing Functions Level 1"
Updated•5 years ago
|
Priority: -- → P2
Comment 1•5 years ago
|
||
Closing; this is now tracked at https://github.com/mdn/sprints/issues/997
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•