Closed
Bug 1775351
Opened 2 years ago
Closed 2 years ago
`linear(...)` easing: Computed value should split linear stop value into two if for entries with both `linear-stop-length` set
Categories
(Core :: CSS Transitions and Animations, defect)
Core
CSS Transitions and Animations
Tracking
()
RESOLVED
FIXED
104 Branch
Tracking | Status | |
---|---|---|
firefox104 | --- | fixed |
People
(Reporter: dshin, Assigned: dshin)
References
Details
Attachments
(2 files)
As per comment thread https://github.com/w3c/csswg-drafts/pull/6533/files#r900402431
This matches the behaviour of linear-gradient
.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Summary: `linear(...)` easing: Computed value should split linear stop values if both `linear-stop-length` are set → `linear(...)` easing: Computed value should split linear stop value into two if for entries with both `linear-stop-length` set
Assignee | ||
Updated•2 years ago
|
Severity: -- → S3
Assignee | ||
Comment 1•2 years ago
|
||
This brings the behaviour inline with linear-gradient(...)
Updated•2 years ago
|
Attachment #9282281 -
Attachment description: Bug 1775351: `linear(...)` easing: Computed value should split linear stop value into two if for entries with both `linear-stop-length` set. r=emilio → Bug 1775351: Part 1: `linear(...)` easing: Computed value should split linear stop value into two if for entries with both `linear-stop-length` set. r=emilio
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D149926
Updated•2 years ago
|
Attachment #9282281 -
Attachment description: Bug 1775351: Part 1: `linear(...)` easing: Computed value should split linear stop value into two if for entries with both `linear-stop-length` set. r=emilio → Bug 1775351: Part 1: `linear(...)` easing: Parsing should split a linear stop value into two for entries with both `linear-stop-length` set. r=emilio
Pushed by dshin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e900fb167e26 Part 1: `linear(...)` easing: Parsing should split a linear stop value into two for entries with both `linear-stop-length` set. r=emilio https://hg.mozilla.org/integration/autoland/rev/4afc18c58426 Part 2: `linear(...)` easing: Simplify piecewise linear implementation given parsing simplification. r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/34585 for changes under testing/web-platform/tests
Comment 5•2 years ago
|
||
Backed out for causing build bustages
- Backout link
- Push with failures
- Failure Log
- Failure line: gmake[4]: *** [/builds/worker/checkouts/gecko/config/makefiles/rust.mk:469: force-cargo-test-run] Error 101
Flags: needinfo?(dshin)
Assignee | ||
Comment 6•2 years ago
•
|
||
Collided with another change from me that landed. My bad - Fix ETA when bug 1775335 lands on central
Flags: needinfo?(dshin)
Upstream PR was closed without merging
Pushed by dshin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1d15e87bbdb1 Part 1: `linear(...)` easing: Parsing should split a linear stop value into two for entries with both `linear-stop-length` set. r=emilio https://hg.mozilla.org/integration/autoland/rev/009e9166463b Part 2: `linear(...)` easing: Simplify piecewise linear implementation given parsing simplification. r=emilio
Comment 9•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1d15e87bbdb1
https://hg.mozilla.org/mozilla-central/rev/009e9166463b
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox104:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•