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
On Wednesday, July 3, 2024 at 10:47:21 AM UTC+2 Anders Hartvoll Ruud wrote:Contact 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).
Just to clarify - this removes the inset-area function?
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:
Do you know if this was used in a production site?From the name, one can assume it's a demo site..
On Wed, Jul 3, 2024 at 11:35 AM Yoav Weiss (@Shopify) <yoav...@chromium.org> wrote:On Wednesday, July 3, 2024 at 10:47:21 AM UTC+2 Anders Hartvoll Ruud wrote:Contact 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).
Just to clarify - this removes the inset-area function?Yes, correct.
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:
Do you know if this was used in a production site?From the name, one can assume it's a demo site..It's just the input for the view to show the features supported by the browser e.g.: https://css3test.com/#css-anchor-position-1It doesn't count as "production use" IMO. Also, I sent a PR to update it: https://github.com/LeaVerou/css3test/pull/249
LGTM2
/Daniel
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2Ba%2BW6mFB9LLuu5eh6HwLg%2BHu7HxzoH-p73%2B38MnGSiyg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/65a95f8b-ac2c-42dd-b016-0a0c44b0e55c%40gmail.com.