clones/sass
1
0
Fork 0
mirror of https://github.com/sass/sass.git synced 2024-09-21 10:37:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Module System] Drop support for CSS-compatibility overloads

Browse Source 
Closes #2703
This commit is contained in:
Natalie Weizenbaum 2019-06-19 15:12:11 -07:00
parent 9e4760ab29
commit 0139632410
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
accepted/module-system.changes.md
View File

@ -12,6 +12,9 @@
* Add `extend()` to `sass:selector`. This is the same as the global
`selector-extend()` function.
* The `sass:color` functions `grayscale()`, `invert()`, `alpha()`, and
`opacity()` no longer allow non-color arguments.
* Describe how to resolve built-in global functions and mixins.
## Draft 5

8
accepted/module-system.md
View File

@ -1579,6 +1579,14 @@ the user use `color.adjust()` instead.
> Once the module system is firmly in place, we may add new `color.lighten()`
> *et al* functions that are shorthands for `color.scale()` instead.
The `grayscale()`, `invert()`, `alpha()`, and `opacity()` functions in
`sass:color` will only accept color arguments, unlike their global counterparts.
> These global functions need to accept non-color arguments for compatibility
> with CSS functions of the same names. Since module namespacing eliminates the
> ambiguity between built-in Sass functions and plain CSS functions, this
> compatibility is no longer necessary.
Built-in modules will contain only the functions described above. They won't
contain any other [members](#member), CSS, or extensions. New members may be
added in the future, but CSS will not be added to existing modules.