Skip to content

[css-cascade] Clarify how @import behaves with invalid rules #5313 #5358

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 1 commit into from
Aug 14, 2020

Conversation

andreubotella
Copy link
Member

@andreubotella andreubotella commented Jul 24, 2020

This change also modifies the mention of @charset as an example of an at-rule with restrictions on its relative ordering to replace it with@namespace, since @charset is no longer considered an at-rule.

Fixes #5313

This change also modifies the mention of @charset as an example of an
at-rule with restrictions on its relative ordering to replace it with
@namespace, since @charset is no longer a valid rule.

Closes w3c#5313.
@fantasai fantasai changed the title [css-cascade][editorial] Clarify how @import behaves with invalid rules [css-cascade] Clarify how @import behaves with invalid rules Aug 14, 2020
@fantasai fantasai changed the title [css-cascade] Clarify how @import behaves with invalid rules [css-cascade] Clarify how @import behaves with invalid rules #5313 Aug 14, 2020
@fantasai fantasai merged commit 3e291e6 into w3c:master Aug 14, 2020
@andreubotella andreubotella deleted the cascade_import-and-charset branch August 15, 2020 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[css-cascade] Clarify when an @import rule is valid
3 participants