On 2/18/25 8:28 AM, Chromestatus wrote:
Contact emails
sakha...@chromium.org
Explainer
None
Specification
https://www.w3.org/TR/css-values-4/#sign-funcs
Summary
The sign-related functions abs() and sign() compute various
functions related to the sign of their argument. The abs(A) function
contains one calculation A, and returns the absolute value of A, as
the same type as the input: if A’s numeric value is positive or 0⁺,
just A again; otherwise -1 * A. The sign(A) function contains one
calculation A, and returns -1 if A’s numeric value is negative, +1 if
A’s numeric value is positive, 0⁺ if A’s numeric value is 0⁺, and 0⁻
if A’s numeric value is 0⁻. The return type is a <number>, made
consistent with the input calculation’s type.
Blink component
Blink>CSS
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink>CSS%22>
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
None
/Gecko/: Shipped/Shipping
/WebKit/: Shipped/Shipping
/Web developers/: Strongly positive
https://issues.chromium.org/issues/40253181#comment9
https://issues.chromium.org/issues/40253181#comment10
/Other signals/:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such
that it has potentially high risk for Android WebView-based applications?
None
Debuggability
None
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
https://wpt.fyi/css/css-values/signs-abs-computed.html
I see there's 6 tests near the bottom that all browsers are failing.
What's up with that?
Flag name on about://flags
CSSSignRelatedFunctions
Finch feature name
None
Non-finch justification
None
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/40253181
Estimated milestones
Shipping on desktop 135
Shipping on Android 135
Shipping on WebView 135
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5091423843778560?gate=5117360513744896
This intent message was generated by Chrome Platform Status
<https://chromestatus.com>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67b48aed.2b0a0220.393e4c.08de.GAE%40google.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67b48aed.2b0a0220.393e4c.08de.GAE%40google.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/13b7d977-76a5-4f14-aa9b-e1bc8c6f813e%40chromium.org.
