-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS Nesting #420
Comments
For survey data and web developer demand, in State of CSS 2023, CSS Nesting was a very common answer to the question "Are there any existing CSS features that you have difficulties using (or avoid altogether) because of lack of support, or differences between browsers?" Also, in preliminary results from State of HTML 2023, CSS Nesting was a somewhat common response to the freeform question "Which existing HTML features or browser APIs are you unable to use because of browser differences or lack of support?" To answer CSS Nesting was to ignore the scope of the question, but it says something nevertheless. |
We'd need to also include these tests:
|
@CanadaHonk Was this confusion related to relaxed nesting not being supported in all browsers? Or was it something else? I'm trying to figure out which aspects of css-nesting we need to focus on. In particular, we can not look at the current set of WPTs and assume that they cover what they need to cover. Also, we're now (apparently) going to change some fundamental parts of css-nesting, although we're not sure how yet. This would make sense to include as well, but we probably need to first confirm that we indeed can make this change at all. |
We should probably ensure that we have a WPT for |
I have some in https://bugzilla.mozilla.org/show_bug.cgi?id=1850974 |
Yes. If the spec is not clear, this might have to get delayed until 2025? Or maybe focus on the parts which are stable? |
We could at least include the relaxed nesting part. All known issues related to that are resolved and tested by WPTs. |
I suggest that we only include tests from these two relevant sub-areas:
In other words:
Deliberately not included, regardless of the current interop situation in wpt.fyi:
|
The list of tests for nesting are from here: web-platform-tests/interop#420 (comment)
Here's a single view of the tests suggested in #420 (comment): |
This comment was marked as resolved.
This comment was marked as resolved.
The list of tests for nesting are from here: web-platform-tests/interop#420 (comment)
The list of tests for nesting are from here: web-platform-tests/interop#420 (comment)
…estonly Automatic update from web-platform-tests Map even more tests to web-features (#43390) The list of tests for nesting are from here: web-platform-tests/interop#420 (comment) -- wpt-commits: 6495c91853a3cf028a401cf4d228fc0b6a5465e4 wpt-pr: 43390
…estonly Automatic update from web-platform-tests Map even more tests to web-features (#43390) The list of tests for nesting are from here: web-platform-tests/interop#420 (comment) -- wpt-commits: 6495c91853a3cf028a401cf4d228fc0b6a5465e4 wpt-pr: 43390
…estonly Automatic update from web-platform-tests Map even more tests to web-features (#43390) The list of tests for nesting are from here: web-platform-tests/interop#420 (comment) -- wpt-commits: 6495c91853a3cf028a401cf4d228fc0b6a5465e4 wpt-pr: 43390 UltraBlame original commit: a52295e0345c455a8beb63d8aa3a1b39dab52e6b
…estonly Automatic update from web-platform-tests Map even more tests to web-features (#43390) The list of tests for nesting are from here: web-platform-tests/interop#420 (comment) -- wpt-commits: 6495c91853a3cf028a401cf4d228fc0b6a5465e4 wpt-pr: 43390 UltraBlame original commit: a52295e0345c455a8beb63d8aa3a1b39dab52e6b
…estonly Automatic update from web-platform-tests Map even more tests to web-features (#43390) The list of tests for nesting are from here: web-platform-tests/interop#420 (comment) -- wpt-commits: 6495c91853a3cf028a401cf4d228fc0b6a5465e4 wpt-pr: 43390 UltraBlame original commit: a52295e0345c455a8beb63d8aa3a1b39dab52e6b
This proposal has been accepted as part of Interop 2024! On behalf of the entire Interop team, thank you for proposing it. You’ll be able to track progress on this topic throughout the year via the Interop 2024 dashboard. |
Thank you for proposing CSS Nesting for inclusion in Interop 2024. We are pleased to let you know that this proposal was accepted as part of the CSS Nesting focus area. You can follow the progress of this focus area on the Interop 2024 dashboard. For an overview of our process, see the proposal selection. Thank you for contributing to Interop 2024! Posted on behalf of the Interop team. |
The list of tests for nesting are from here: web-platform-tests/interop#420 (comment)
Description
CSS Nesting is currently supported by all engines but they have varying implementations (from different spec snapshots).
Specification
https://www.w3.org/TR/css-nesting-1/
Open Issues
// todo
Tests
https://wpt.fyi/results/css/css-nesting
Current Implementations
Standards Positions
Gecko: mozilla/standards-positions#695
WebKit: WebKit/standards-positions#69
Browser bug reports
Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1095675
Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1648037
WebKit: https://bugs.webkit.org/show_bug.cgi?id=223497
Developer discussions
Seen some discussion online of Gecko and Blink having different implementations (from varying spec at the time), seems to cause confusion with nesting.
Polls & Surveys
State of CSS 2023: https://2023.stateofcss.com/en-US/features/
Existing Usage
https://chromestatus.com/metrics/feature/timeline/popularity/4372 (this seems odd?)
Workarounds
Use a preprocessor like PostCSS.
Accessibility Impact
N/A
Privacy Impact
N/A
Other
The text was updated successfully, but these errors were encountered: