Closed
Bug 1820412
Opened 2 years ago
Closed 2 years ago
Comp funcs (min/max/clamp) should handle NaN contagiously
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
113 Branch
People
(Reporter: canadahonk, Assigned: canadahonk)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
NaN should be contagious (always the result) in comp funcs (min/max/clamp).
WPT tests which check for this behavior:
- https://wpt.fyi/results/css/css-values/calc-infinity-nan-computed.html
- https://wpt.fyi/results/css/css-values/calc-infinity-nan-serialize-angle.html
- https://wpt.fyi/results/css/css-values/calc-infinity-nan-serialize-length.html
- https://wpt.fyi/results/css/css-values/calc-infinity-nan-serialize-time.html
(possibly more subtests in various others)
Assignee | ||
Updated•2 years ago
|
Summary: Comp funcs (min/max/clamp) should handle NaN contagiously → Comp funcs (min/max/clamp) should always return NaN
Assignee | ||
Updated•2 years ago
|
Summary: Comp funcs (min/max/clamp) should always return NaN → Comp funcs (min/max/clamp) should always return NaN if given as a value
Assignee | ||
Updated•2 years ago
|
Summary: Comp funcs (min/max/clamp) should always return NaN if given as a value → Comp funcs (min/max/clamp) should handle NaN contagiously
Assignee | ||
Comment 1•2 years ago
|
||
If NaN is given as any input to CSS comp funcs (min/max/clamp), it
should return NaN.
Adjusted WPT test expectations, 4 newly pass :tada:
(and more when other types get NaN support later)
Depends on D171658
Updated•2 years ago
|
Assignee: nobody → oj
Status: NEW → ASSIGNED
Updated•2 years ago
|
Severity: -- → S3
Assignee | ||
Updated•2 years ago
|
Blocks: calc-nan-inf
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c1e40ba0719d
CSS comp funcs should handle NaN contagiously r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/39240 for changes under testing/web-platform/tests
Comment 4•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
Upstream PR merged by moz-wptsync-bot
Updated•2 years ago
|
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•