-
Notifications
You must be signed in to change notification settings - Fork 233
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
Document the moz-document breaking change on the sass website. #667
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add an entry in data/documentation.yml
?
--- | ||
|
||
Sass has historically supported a special parsing for the `@-moz-document` rule. | ||
As [Firefox dropped support for them], Sass will also drop support. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per this comment - sass/dart-sass#378 (comment)
Sass won't drop support entirely, only for the special parsing in favor of interpolation within unknown at-rules
42c7281
to
d89ab68
Compare
d89ab68
to
5f3180e
Compare
@Goodwine updated |
Currently, the link in the deprecation warning goes to a website that does not even exist anymore, relying on the web-archive. And this website does not give any details about the Sass breaking change.
This references this breaking change on the website like the others (still linking to the Firefox deprecation announcement on web-archive as part of the explanation).