This feature extends the existing contain-intrinsic-size syntax: none | <length> | auto && <length> to also include auto && none: none | <length> | auto && <length> | auto && none The reason for this change is the CSSWG resolution (https://github.com/w3c/csswg-drafts/issues/8407#issuecomment-1440466558) to add an interaction between content-visibility: auto and contain-intrinsic-size. Specifically, that the former adds an "auto" keyword to the latter. For this to work, the resolution includes a note to extend contain-intrinsic-size syntax for "auto" to work with all existing keywords, including "none".
There is a risk of interoperability since the new syntax would previously be considered invalid, and result in a default behavior (equivalent to contain-intrinsic-size: none). Sites currently specifying contain-intrinsic-size: auto none would have their behavior change on Chromium after this feature launches.
I estimate this risk to be low.
None. This is an improvement which will allow future work to improve ergonomics of content-visibility.
None.
None.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
This feature is debuggable in the same way as other CSS features.
M116
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 emails
vmp...@chromium.orgSpecification
NoneSummary
This feature extends the existing contain-intrinsic-size syntax: none | <length> | auto && <length> to also include auto && none: none | <length> | auto && <length> | auto && none The reason for this change is the CSSWG resolution (https://github.com/w3c/csswg-drafts/issues/8407#issuecomment-1440466558) to add an interaction between content-visibility: auto and contain-intrinsic-size. Specifically, that the former adds an "auto" keyword to the latter. For this to work, the resolution includes a note to extend contain-intrinsic-size syntax for "auto" to work with all existing keywords, including "none".
Blink component
Blink>CSSTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
There is a risk of interoperability since the new syntax would previously be considered invalid, and result in a default behavior (equivalent to contain-intrinsic-size: none). Sites currently specifying contain-intrinsic-size: auto none would have their behavior change on Chromium after this feature launches.
I estimate this risk to be low.
Gecko: No signal This change was discussed in CSSWG and there were no objections to the resolutions
WebKit: No signal This change was discussed in CSSWG and there were no objections to the resolutions
--
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/CADsXd2MgWYdmrJ1JHv0rYTWr2wcqUQ%2BZUriH5UQAREw7Wg0Ptg%40mail.gmail.com.
On Fri, Jun 9, 2023 at 10:19 PM 'Vladimir Levin' via blink-dev <blin...@chromium.org> wrote:Contact emails
vmp...@chromium.orgSpecification
NoneSummary
This feature extends the existing contain-intrinsic-size syntax: none | <length> | auto && <length> to also include auto && none: none | <length> | auto && <length> | auto && none The reason for this change is the CSSWG resolution (https://github.com/w3c/csswg-drafts/issues/8407#issuecomment-1440466558) to add an interaction between content-visibility: auto and contain-intrinsic-size. Specifically, that the former adds an "auto" keyword to the latter. For this to work, the resolution includes a note to extend contain-intrinsic-size syntax for "auto" to work with all existing keywords, including "none".
Blink component
Blink>CSSTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
There is a risk of interoperability since the new syntax would previously be considered invalid, and result in a default behavior (equivalent to contain-intrinsic-size: none). Sites currently specifying contain-intrinsic-size: auto none would have their behavior change on Chromium after this feature launches.
I estimate this risk to be low.
Would you be able to confirm that estimate e.g. with an HTTP archive search?
Gecko: No signal This change was discussed in CSSWG and there were no objections to the resolutions
WebKit: No signal This change was discussed in CSSWG and there were no objections to the resolutionsCan you please file signals? I don't believe a CSSWG counts as a positive signal. Also, I don't believe I saw a comment from any WebKit person on the minutes.A signal request would let them know this is being worked on in Chromium.
Thank you for your feedback. My responses are inline belowOn Wed, Jun 14, 2023 at 12:24 AM Yoav Weiss <yoav...@chromium.org> wrote:On Fri, Jun 9, 2023 at 10:19 PM 'Vladimir Levin' via blink-dev <blin...@chromium.org> wrote:Contact emails
vmp...@chromium.orgSpecification
NoneSummary
This feature extends the existing contain-intrinsic-size syntax: none | <length> | auto && <length> to also include auto && none: none | <length> | auto && <length> | auto && none The reason for this change is the CSSWG resolution (https://github.com/w3c/csswg-drafts/issues/8407#issuecomment-1440466558) to add an interaction between content-visibility: auto and contain-intrinsic-size. Specifically, that the former adds an "auto" keyword to the latter. For this to work, the resolution includes a note to extend contain-intrinsic-size syntax for "auto" to work with all existing keywords, including "none".
Blink component
Blink>CSSTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
There is a risk of interoperability since the new syntax would previously be considered invalid, and result in a default behavior (equivalent to contain-intrinsic-size: none). Sites currently specifying contain-intrinsic-size: auto none would have their behavior change on Chromium after this feature launches.
I estimate this risk to be low.
Would you be able to confirm that estimate e.g. with an HTTP archive search?I'm in the process of figuring out how to do this, and will get back to you with the results when I have them. My estimate stems from the fact that currently "contain-intrinsic-size: auto none" is considered an invalid syntax, making it unlikely to be used as a value.
Thanks in advance,vmpstr
Gecko: No signal This change was discussed in CSSWG and there were no objections to the resolutions
WebKit: No signal This change was discussed in CSSWG and there were no objections to the resolutionsCan you please file signals? I don't believe a CSSWG counts as a positive signal. Also, I don't believe I saw a comment from any WebKit person on the minutes.A signal request would let them know this is being worked on in Chromium.I have filed the following requests for positions:
LGTM2
/Daniel
Excited to see this land; LGTM1
--
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/000000000000138e3105ffbf36a9%40google.com.
LGTM3
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/96e668ee-ced2-e88d-a534-87f3d5b32f49%40gmail.com.