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)

defect

Tracking

()

RESOLVED FIXED
113 Branch
Tracking Status
firefox112 --- wontfix
firefox113 --- fixed

People

(Reporter: canadahonk, Assigned: canadahonk)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Summary: Comp funcs (min/max/clamp) should handle NaN contagiously → Comp funcs (min/max/clamp) should always return NaN
Summary: Comp funcs (min/max/clamp) should always return NaN → Comp funcs (min/max/clamp) should always return NaN if given as a value
Summary: Comp funcs (min/max/clamp) should always return NaN if given as a value → Comp funcs (min/max/clamp) should handle NaN contagiously

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

Assignee: nobody → oj
Status: NEW → ASSIGNED
Severity: -- → S3
Blocks: calc-nan-inf
See Also: → 1823446
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
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
Upstream PR merged by moz-wptsync-bot
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: