Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update the Media 4 deprecation page #685

Merged
merged 1 commit into from
Nov 1, 2022
Merged

Update the Media 4 deprecation page #685

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 8 additions & 10 deletions source/documentation/breaking-changes/media-logic.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,15 @@
---
title: "Breaking Change: Media Queries Level 4"
introduction: >
Sass is adding support for the CSS Media Queries Level 4 specification, but
this conflicts with some Sass-specific syntax. That syntax is deprecated to
ensure that Sass remains fully CSS-compatible.
Sass has added support for the CSS Media Queries Level 4 specification. This
originally conflicted with some Sass-specific syntax, so this syntax was
deprecated and is now interpreted according to the CSS standard.
---

<% impl_status dart: '1.56.0', libsass: false, ruby: false %>

Because Sass supports almost any Sass expression in parenthesized media
conditions, there are a few constructs that could be broken by adding full
conditions, there were a few constructs whose meaning was changed by adding full
support for Media Queries Level 4. Specifically:

* `@media (not (foo))` was historically interpreted by Sass as meaning
Expand All @@ -17,16 +19,12 @@ support for Media Queries Level 4. Specifically:
interpreted as SassScript's logical operators, compiling to `@media (bar)` and
`@media (foo)` respectively.

Fortunately, these are unlikely to come up in practice.
Fortunately, these came up very infrequently in practice.

## Transition Period

<% impl_status dart: '1.54.0', libsass: false, ruby: false %>

First, we'll emit deprecation warnings for the previous ambiguous cases. These
First, we emitted deprecation warnings for the previous ambiguous cases. These
will have suggestions for how to preserve the existing behavior or how to use
the new CSS syntax.

Once the deprecation warnings have been out for at least three months, we'll
release a version that exclusively interprets these ambiguous cases according to
the CSS spec.