Replaces the inset-area() function with inset-area values directly within position-try-fallbacks. This means that you now just write e.g. position-try-fallbacks:top instead of position-try-fallbacks:inset-area(top).
The CSSWG made this change shortly after CSS Anchor Positioning shipped in Blink:
https://github.com/w3c/csswg-drafts/issues/10320#issuecomment-2137882897
Searching for existing cases of "inset-area(" in HTTP Archive, I found just a single match out of 638589186 rows:
Query used:
#standardSQL
SELECT response_bodies.url
FROM `httparchive.response_bodies.2024_06_01_desktop` AS response_bodies
WHERE REGEXP_CONTAINS(response_bodies.response_body, r'inset\-area\(')
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
Shipping on desktop | 128 |
Shipping on Android | 128 |
Shipping on WebView | 128 |
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).
NoneContact emailsand...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/css-anchor-position-1/#position-try-fallbacks
SummaryReplaces the inset-area() function with inset-area values directly within position-try-fallbacks. This means that you now just write e.g. position-try-fallbacks:top instead of position-try-fallbacks:inset-area(top).
The CSSWG made this change shortly after CSS Anchor Positioning shipped in Blink:
https://github.com/w3c/csswg-drafts/issues/10320#issuecomment-2137882897
Blink componentBlink>CSS
TAG reviewNone
TAG review statusNot applicable
Risks
Interoperability and Compatibility
Searching for existing cases of "inset-area(" in HTTP Archive, I found just a single match out of 638589186 rows:
Query used:
#standardSQL
SELECT response_bodies.url
FROM `httparchive.response_bodies.2024_06_01_desktop` AS response_bodies
WHERE REGEXP_CONTAINS(response_bodies.response_body, r'inset\-area\(')
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
WebView application risksDoes this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
DebuggabilityNone
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?No
Is this feature fully tested by web-platform-tests?Yes
Flag name on chrome://flagsNone
Finch feature nameCSSInsetAreaValue
Requires code in //chrome?False
Estimated milestonesShipping on desktop128Shipping on Android128Shipping on WebView128
Anticipated spec changesOpen 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 Statushttps://chromestatus.com/feature/5116199771045888?gate=5071381116223488