[math functions] remove incorrect tests

[danielsakhapov]

Test List

https://wpt.fyi/results/css/css-values/exp-log-serialize.html and https://wpt.fyi/results/css/css-values/round-mod-rem-serialize.html

Rationale

We can't expect -infinity and NaN as a computed value for opacity and transform, so I propose either to remove them or test only the specified value.

[foolip]

@danielsakhapov can these tests be updated in some way, or is there no pass condition that makes sense?

[danielsakhapov]

@foolip we can test only for the specified value and not the computed one.

[foolip]

Thanks @danielsakhapov!

@jgraham can you handle this proposal for Gecko?
@gsnedders @nt1m can you handle this proposal for WebKit?

[foolip]

To make it clear, the proposal would be to only keep the tests for specified value in Interop 2023. Tests for the computed value would be removed or split out.

[jgraham]

@emilio does removing the computed value tests seem reasonable here? Should we be testing some other behaviour instead?

[emilio]

We should probably test that those produce what the spec says, which IIRC is that NaN computes to 0, and that infinity / -infinity compute to a very large (or small, respectively) but finite number.

cc @CanadaHonk

[nmoucht]

We should probably test that those produce what the spec says, which IIRC is that NaN computes to 0, and that infinity / -infinity compute to a very large (or small, respectively) but finite number.

cc @CanadaHonk

I agree that we should change the computed value tests based on the language in the spec here:

By definition, ±∞ are outside the allowed range for any property, and will clamp to the minimum/maximum value allowed. Even properties that can explicitly represent infinity as a keyword value, such as animation-iteration-count, will end up clamping ±∞, as math functions can’t resolve to keyword values; the numeric part of the property’s syntax still has a minimum/maximum value.

[danielsakhapov]

@emilio Please have a look at my change web-platform-tests/wpt#40567