Skip to content

[css-conditional-3][css-conditional-4] Create a css-conditional-4 draft, and dispose of the features in css-conditional-3 marked for moving to level 4. #3777

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

Merged
merged 2 commits into from
Mar 29, 2019

Conversation

dbaron
Copy link
Member

@dbaron dbaron commented Mar 29, 2019

[css-conditional-3][css-conditional-4] Create a css-conditional-4 draft, and dispose of the features in css-conditional-3 marked for moving to level 4.

There were two commented-out features in css-conditional-3 marked as being deferred to level 4. These are removed from the draft, but NOT added in css-conditional-4, because:

Also correct a few bits of metadata in css-conditional-3.

This is being done as part of the resolution in #3207 (comment)

…ft, and dispose of the features in css-conditional-3 marked for moving to level 4.

There were two commented-out features in css-conditional-3 marked as
being deferred to level 4.  These are removed from the draft, but NOT
added in css-conditional-4, because:

- the `@import` `supports()` syntax is already in
  https://drafts.csswg.org/css-cascade-4/#at-ruledef-import

- the addition of an `@document` rule is probably no longer desirable
  given the discussion and removal in
  https://bugzilla.mozilla.org/show_bug.cgi?id=1035091 which was the
  only implementation.

Also correct a few bits of metadata in css-conditional-3.

This is being done as part of the resolution in
w3c#3207 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants