Skip to content

Latest commit

 

History

History
2425 lines (1702 loc) · 78 KB

SASS_CHANGELOG.md

File metadata and controls

2425 lines (1702 loc) · 78 KB
Raw

Sass Changelog

  • Table of contents {:toc}

3.1.19 (Unreleased)

  • Fix an uninitialized constant Sass::Exec::Sass::Util error when using the command-line tool.
  • Allow @extend within directives such as @media as long as it only extends selectors that are within the same directive.

3.1.18

Deprecations -- Must Read!

  • Deprecate the use of @extend within directives such as @media. This has never worked correctly, and now it's officially deprecated. It will be an error in 3.2.

3.1.17

  • Don't crash when calling #inspect on an internal Sass tree object in Ruby 1.9.
  • Fix some bugs in sass --watch introduced in 3.1.16. Thanks to Maher Sallam.
  • Support bare interpolation in the value portion of attribute selectors (e.g. [name=#{$value}]).
  • Support keyword arguments for the invert() function.
  • Handle backslash-separated paths better on Windows.
  • Fix rake install on Ruby 1.9.
  • Properly convert nested @if statements with sass-convert.

3.1.16

  • Fix some bugs in sass-convert selector parsing when converting from CSS.
  • Substantially improve compilation performance on Ruby 1.8.
  • Support the @-moz-document directive's non-standard url-prefix and domain function syntax.
  • Support the @supports directive.
  • Fix a performance issue when using /*! */ comments with the Rails asset pipeline.
  • Support -moz-element.
  • Properly handle empty lists in sass-convert.
  • Move from FSSM to Listen for file-system monitoring.

3.1.15

  • Support extending multiple comma-separated selectors (e.g. @extend .foo, .bar). This is just a terser way to write multiple @extends (e.g. @extend .foo; @extend .bar). This wasn't previously intended to work, but it did in the indented syntax only.
  • Avoid more stack overflows when there are import loops in files.
  • Update the bundled FSSM to version 0.2.8.1.
  • Make the grayscale function work with -webkit-filter.
  • Provide a better error message for selectors beginning with / in the indented syntax.
  • Flush standard output after printing notifications in sass --watch.
  • Fix variable definitions in the REPL.

3.1.14

  • Fix a typo that was causing crashes on Ruby 1.9.

3.1.13

  • Fix a smattering of subtle bugs that would crop up when using multibyte character sets.
  • Fix a bug when using @extend with selectors containing newlines.
  • Make boolean operators short-circuit.
  • Remove unnecessary whitespace in selectors in :compressed mode.
  • Don't output debug info within non-@media directives.
  • Make sure :after and :before selectors end up on the end of selectors resulting from @extend.
  • Fix a bug when using imports containing invalid path characters on Windows.
  • Bubble CSS @import statements to the top of stylesheets.

Deprecations -- Must Read!

  • Using #{} interpolation in @import directives will, as of Sass 3.2, require that the @import directive use url() rather than a plain string. The old way is deprecated and will print a warning.

3.1.12

  • Compatibility with the mathn library (thanks to Thomas Walpole).
  • Fix some infinite loops with mixins that were previously uncaught.
  • Catch infinite @import loops.
  • Fix a deprecation warning in sass --update and --watch (thanks to Marcel Köppen).
  • Don't make $important a special pre-initialized variable.
  • Fix exponential parsing time of certain complex property values and selectors.
  • Properly merge @media directives with comma-separated queries. E.g. @media foo, bar { @media baz { ... } } now becomes @media foo and baz, bar and baz { ... }.

3.1.11

  • Allow control directives (such as @if) to be nested beneath properties.
  • Allow property names to begin with a hyphen followed by interpolation (e.g. -#{...}).
  • Fix a parsing error with interpolation in comma-separated lists.
  • Make --cache-store with with --update.
  • Properly report ArgumentErrors that occur within user-defined functions.
  • Don't crash on JRuby if the underlying Java doesn't support every Unicode encoding.
  • Add new updated_stylesheet callback, which is run after each stylesheet has been successfully compiled. Thanks to Christian Peters.
  • Allow absolute paths to be used in an importer with a different root.
  • Don't destructively modify the options when running Sass::Plugin.force_update.
  • Prevent Regexp buffer overflows when parsing long strings (thanks to Agworld.

Deprecations -- Must Read!

  • The updating_stylesheet is deprecated and will be removed in a future release. Use the new updated_stylesheet callback instead.

3.1.10

  • Fix another aspect of the 3.1.8 regression relating to +.

3.1.9

  • Fix a regression in 3.1.8 that broke the + combinator in selectors.

  • Deprecate the loud-comment flag when used with silent comments (e.g. //!). Using it with multi-line comments (e.g. /*!) still works.

3.1.8

  • Deprecate parent selectors followed immediately by identifiers (e.g. &foo). This should never have worked, since it violates the rule of & only being usable where an element selector would.

  • Add a --force option to the sass executable which makes --update always compile all stylesheets, even if the CSS is newer.

  • Disallow semicolons at the end of @import directives in the indented syntax.

  • Don't error out when being used as a library without requiring fileutil.

  • Don't crash when Compass-style sprite imports are used with StalenessChecker (thanks to Matthias Bauer).

  • The numeric precision of numbers in Sass can now be set using the --precision option to the command line. Additionally, the default number of digits of precision in Sass output can now be changed by setting Sass::Script::Number.precision to an integer (defaults to 3). Since this value can now be changed, the PRECISION constant in Sass::Script::Number has been deprecated. In the unlikely event that you were using it in your code, you should now use Sass::Script::Number.precision_factor instead.

  • Don't crash when running sass-convert with selectors with two commas in a row.

  • Explicitly require Ruby >= 1.8.7 (thanks Eric Mason).

  • Properly validate the nesting of elements in imported stylesheets.

  • Properly compile files in parent directories with --watch and --update.

  • Properly null out options in mixin definitions before caching them. This fixes a caching bug that has been plaguing some Rails 3.1 users.

3.1.7

  • Don't crash when doing certain operations with @functions.

3.1.6

  • The option :trace_selectors can now be used to emit a full trace before each selector. This can be helpful for in-browser debugging of stylesheet imports and mixin includes. This option supersedes the :line_comments option and is superseded by the :debug_info option.

  • Fix a bug where long @if/@else chains would cause exponential slowdown under some circumstances.

3.1.5

  • Updated the vendored FSSM version, which will avoid segfaults on OS X Lion when using --watch.

3.1.4

  • Sass no longer unnecessarily caches the sass options hash. This allows objects that cannot be marshaled to be placed into the options hash.

3.1.3

  • Sass now logs message thru a logger object which can be changed to provide integration with other frameworks' logging infrastructure.

3.1.2

  • Fix some issues that were breaking Sass when running within Rubinius.
  • Fix some issues that were affecting Rails 3.1 integration.
  • New function zip allows several lists to be combined into one list of lists. For example: zip(1px 1px 3px, solid dashed solid, red green blue) becomes 1px solid red, 1px dashed green, 3px solid blue
  • New function index returns the list index of a value within a list. For example: index(1px solid red, solid) returns 2. When the value is not found false is returned.

3.1.1

  • Make sure Sass::Plugin is loaded at the correct time in Rails 3.

3.1.0

  • Add an {Sass::Script::Functions#invert invert function} that takes the inverse of colors.

  • A new sass function called if can be used to emit one of two values based on the truth value of the first argument. For example, if(true, 1px, 2px) returns 1px and if(false, 1px, 2px) returns 2px.

  • Compass users can now use the --compass flag to make the Compass libraries available for import. This will also load the Compass project configuration if run from the project root.

  • Many performance optimizations have been made by thedarkone.

  • Allow selectors to contain extra commas to make them easier to modify. Extra commas will be removed when the selectors are converted to CSS.

  • @import may now be used within CSS or @media rules. The imported file will be treated as though it were nested within the rule. Files with mixins may not be imported in nested contexts.

  • If a comment starts with !, that comment will now be interpolated (#{...} will be replaced with the resulting value of the expression inside) and the comment will always be printed out in the generated CSS file -- even with compressed output. This is useful for adding copyright notices to your stylesheets.

  • A new executable named scss is now available. It is exactly like the sass executable except it defaults to assuming input is in the SCSS syntax. Both programs will use the source file's extension to determine the syntax where possible.

Sass-based Functions

While it has always been possible to add functions to Sass with Ruby, this release adds the ability to define new functions within Sass files directly. For example:

$grid-width: 40px;
$gutter-width: 10px;

@function grid-width($n) {
  @return $n * $grid-width + ($n - 1) * $gutter-width;
}

#sidebar { width: grid-width(5); }

Becomes:

#sidebar {
  width: 240px; }

Keyword Arguments

Both mixins and Sass functions now support the ability to pass in keyword arguments. For example, with mixins:

@mixin border-radius($value, $moz: true, $webkit: true, $css3: true) {
  @if $moz { -moz-border-radius: $value }
  @if $webkit { -webkit-border-radius: $value }
  @if $css3 { border-radius: $value }
}

@include border-radius(10px, $webkit: false);

And with functions:

p {
  color: hsl($hue: 180, $saturation: 78%, $lightness: 57%);
}

Keyword arguments are of the form $name: value and come after normal arguments. They can be used for either optional or required arguments. For mixins, the names are the same as the argument names for the mixins. For functions, the names are defined along with the functions. The argument names for the built-in functions are listed {Sass::Script::Functions in the function documentation}.

Sass functions defined in Ruby can use the {Sass::Script::Functions.declare} method to declare the names of the arguments they take.

New Keyword Functions

The new keyword argument functionality enables new Sass color functions that use keywords to encompass a large amount of functionality in one function.

  • The {Sass::Script::Functions#adjust_color adjust-color} function works like the old lighten, saturate, and adjust-hue methods. It increases and/or decreases the values of a color's properties by fixed amounts. For example, adjust-color($color, $lightness: 10%) is the same as lighten($color, 10%): it returns $color with its lightness increased by 10%.

  • The {Sass::Script::Functions#scale_color scale_color} function is similar to {Sass::Script::Functions#adjust adjust}, but instead of increasing and/or decreasing a color's properties by fixed amounts, it scales them fluidly by percentages. The closer the percentage is to 100% (or -100%), the closer the new property value will be to its maximum (or minimum). For example, scale-color(hsl(120, 70, 80), $lightness: 50%) will change the lightness from 80% to 90%, because 90% is halfway between 80% and 100%. Similarly, scale-color(hsl(120, 70, 50), $lightness: 50%) will change the lightness from 50% to 75%.

  • The {Sass::Script::Functions#change_color change-color} function simply changes a color's properties regardless of their old values. For example change-color($color, $lightness: 10%) returns $color with 10% lightness, and change-color($color, $alpha: 0.7) returns color with opacity 0.7.

Each keyword function accepts $hue, $saturation, $value, $red, $green, $blue, and $alpha keywords, with the exception of scale-color() which doesn't accept $hue. These keywords modify the respective properties of the given color.

Each keyword function can modify multiple properties at once. For example, adjust-color($color, $lightness: 15%, $saturation: -10%) both lightens and desaturates $color. HSL properties cannot be modified at the same time as RGB properties, though.

Lists

Lists are now a first-class data type in Sass, alongside strings, numbers, colors, and booleans. They can be assigned to variables, passed to mixins, and used in CSS declarations. Just like the other data types (except booleans), Sass lists look just like their CSS counterparts. They can be separated either by spaces (e.g. 1px 2px 0 10px) or by commas (e.g. Helvetica, Arial, sans-serif). In addition, individual values count as single-item lists.

Lists won't behave any differently in Sass 3.1 than they did in 3.0. However, you can now do more with them using the new list functions:

  • The {Sass::Script::Functions#nth nth($list, $n) function} returns the nth item in a list. For example, nth(1px 2px 10px, 2) returns the second item, 2px. Note that lists in Sass start at 1, not at 0 like they do in some other languages.

  • The {Sass::Script::Functions#join join($list1, $list2) function} joins together two lists into one. For example, join(1px 2px, 10px 5px) returns 1px 2px 10px 5px.

  • The {Sass::Script::Functions#append append($list, $val) function} appends values to the end of a list. For example, append(1px 2px, 10px) returns 1px 2px 10px.

  • The {Sass::Script::Functions#join length($list) function} returns the length of a list. For example, length(1px 2px 10px 5px) returns 4.

For more details about lists see {file:SASS_REFERENCE.md#lists the reference}.

@each

There's also a new directive that makes use of lists. The {file:SASS_REFERENCE.md#each-directive @each directive} assigns a variable to each item in a list in turn, like @for does for numbers. This is useful for writing a bunch of similar styles without having to go to the trouble of creating a mixin. For example:

@each $animal in puma, sea-slug, egret, salamander {
  .#{$animal}-icon {
    background-image: url('/images/#{$animal}.png');
  }
}

is compiled to:

.puma-icon {
  background-image: url('/images/puma.png'); }
.sea-slug-icon {
  background-image: url('/images/sea-slug.png'); }
.egret-icon {
  background-image: url('/images/egret.png'); }
.salamander-icon {
  background-image: url('/images/salamander.png'); }

@media Bubbling

Modern stylesheets often use @media rules to target styles at certain sorts of devices, screen resolutions, or even orientations. They're also useful for print and aural styling. Unfortunately, it's annoying and repetitive to break the flow of a stylesheet and add a @media rule containing selectors you've already written just to tweak the style a little.

Thus, Sass 3.1 now allows you to nest @media rules within selectors. It will automatically bubble them up to the top level, putting all the selectors on the way inside the rule. For example:

.sidebar {
  width: 300px;
  @media screen and (orientation: landscape) {
    width: 500px;
  }
}

is compiled to:

.sidebar {
  width: 300px;
}
@media screen and (orientation: landscape) {
  .sidebar {
    width: 500px;
  }
}

You can also nest @media directives within one another. The queries will then be combined using the and operator. For example:

@media screen {
  .sidebar {
    @media (orientation: landscape) {
      width: 500px;
    }
  }
}

is compiled to:

@media screen and (orientation: landscape) {
  .sidebar {
    width: 500px;
  }
}

Nested @import

The @import statement can now be nested within other structures such as CSS rules and @media rules. For example:

@media print {
  @import "print";
}

This imports print.scss and places all rules so imported within the @media print block. This makes it easier to create stylesheets for specific media or sections of the document and distributing those stylesheets across multiple files.

Backwards Incompatibilities -- Must Read!

  • When @import is given a path without .sass, .scss, or .css extension, and no file exists at that path, it will now throw an error. The old behavior of becoming a plain-CSS @import was deprecated and has now been removed.

  • Get rid of the --rails flag for the sass executable. This flag hasn't been necessary since Rails 2.0. Existing Rails 2.0 installations will continue to work.

  • Removed deprecated support for ! prefixed variables. Use $ to prefix variables now.

  • Removed the deprecated css2sass executable. Use sass-convert now.

  • Removed support for the equals operator in variable assignment. Use : now.

  • Removed the sass2 mode from sass-convert. Users who have to migrate from sass2 should install Sass 3.0 and quiet all deprecation warnings before installing Sass 3.1.

Sass Internals

  • It is now possible to define a custom importer that can be used to find imports using different import semantics than the default filesystem importer that Sass provides. For instance, you can use this to generate imports on the fly, look them up from a database, or implement different file naming conventions. See the {Sass::Importers::Base Importer Base class} for more information.

  • It is now possible to define a custom cache store to allow for efficient caching of Sass files using alternative cache stores like memcached in environments where a writable filesystem is not available or where the cache need to be shared across many servers for dynamically generated stylesheet environments. See the {Sass::CacheStores::Base CacheStore Base class} for more information.

3.0.26 (Unreleased)

  • Fix a performance bug in large SCSS stylesheets with many nested selectors. This should dramatically decrease compilation time of such stylesheets.

  • Upgrade the bundled FSSM to version 0.2.3. This means sass --watch will work out of the box with Rubinius.

3.0.25

Tagged on GitHub.

  • When displaying a Sass error in an imported stylesheet, use the imported stylesheet's contents rather than the top-level stylesheet.

  • Fix a bug that caused some lines with non-ASCII characters to be ignored in Ruby 1.8.

  • Fix a bug where boolean operators (and, or, and not) wouldn't work at the end of a line in a multiline SassScript expression.

  • When using sass --update, only update individual files when they've changed.

3.0.24

Tagged on GitHub.

  • Raise an error when @else appears without an @if in SCSS.

  • Fix some cases where @if rules were causing the line numbers in error reports to become incorrect.

3.0.23

Tagged on GitHub.

  • Fix the error message for unloadable modules when running the executables under Ruby 1.9.2.

@charset Change

The behavior of @charset has changed in version 3.0.23 in order to work around a bug in Safari, where @charset declarations placed anywhere other than the beginning of the document cause some CSS rules to be ignored. This change also makes @charsets in imported files behave in a more useful way.

Ruby 1.9

When using Ruby 1.9, which keeps track of the character encoding of the Sass document internally, @charset directive in the Sass stylesheet and any stylesheets it imports are no longer directly output to the generated CSS. They're still used for determining the encoding of the input and output stylesheets, but they aren't rendered in the same way other directives are.

Instead, Sass adds a single @charset directive at the beginning of the output stylesheet if necessary, whether or not the input stylesheet had a @charset directive. It will add this directive if and only if the output stylesheet contains non-ASCII characters. By default, the declared charset will be UTF-8, but if the Sass stylesheet declares a different charset then that will be used instead if possible.

One important consequence of this scheme is that it's possible for a Sass file to import partials with different encodings (e.g. one encoded as UTF-8 and one as IBM866). The output will then be UTF-8, unless the importing stylesheet declares a different charset.

Ruby 1.8

Ruby 1.8 doesn't have good support for encodings, so it uses a simpler but less accurate scheme for figuring out what @charset declaration to use for the output stylesheet. It just takes the first @charset declaration to appear in the stylesheet or any of its imports and moves it to the beginning of the document. This means that under Ruby 1.8 it's not safe to import files with different encodings.

3.0.22

Tagged on GitHub.

  • Remove vendor/sass, which snuck into the gem by mistake and was causing trouble for Heroku users (thanks to Jacques Crocker).

  • sass-convert now understands better when it's acceptable to remove parentheses from expressions.

3.0.21

Tagged on GitHub.

  • Fix the permissions errors for good.

  • Fix more #options attribute errors.

3.0.20

Tagged on GitHub.

  • Fix some permissions errors.

  • Fix #options attribute errors when CSS functions were used with commas.

3.0.19

Tagged on GitHub.

  • Make the alpha value for rgba colors respect {Sass::Script::Number::PRECISION}.

  • Remove all newlines in selectors in :compressed mode.

  • Make color names case-insensitive.

  • Properly detect SCSS files when using sass -c.

  • Remove spaces after commas in :compressed mode.

  • Allow the --unix-newlines flag to work on Unix, where it's a no-op.

3.0.18

Tagged on GitHub.

  • Don't require rake in the gemspec, for bundler compatibility under JRuby. Thanks to Gordon McCreight.

  • Add a command-line option --stop-on-error that causes Sass to exit when a file fails to compile using --watch or --update.

  • Fix a bug in haml_tag that would allow duplicate attributes to be added and make data- attributes not work.

  • Get rid of the annoying RDoc errors on install.

  • Disambiguate references to the Rails module when haml-rails is installed.

  • Allow @import in SCSS to import multiple files in the same @import rule.

3.0.17

Tagged on GitHub.

  • Disallow #{} interpolation in @media queries or unrecognized directives. This was never allowed, but now it explicitly throws an error rather than just producing invalid CSS.

  • Make sass --watch not throw an error when passed a single file or directory.

  • Understand that mingw counts as Windows.

  • Make sass --update return a non-0 exit code if one or more files being updated contained an error.

3.0.16

Tagged on GitHub.

  • Fix a bug where certain sorts of comments would get improperly rendered in the :compact style.

  • Always allow a trailing */ in loud comments in the indented syntax.

  • Fix a performance issue with SCSS parsing in rare cases. Thanks to Chris Eppstein.

  • Use better heuristics for figuring out when someone might be using the wrong syntax with sass --watch.

3.0.15

Tagged on GitHub.

  • Fix a bug where sass --watch and sass --update were completely broken.

  • Allow @imported values to contain commas.

3.0.14

Tagged on GitHub.

  • Properly parse paths with drive letters on Windows (e.g. C:\Foo\Bar.sass) in the Sass executable.

  • Compile Sass files in a deterministic order.

  • Fix a bug where comments after @if statements in SCSS weren't getting passed through to the output document.

3.0.13

Tagged on GitHub.

CSS @import Directives

Sass is now more intelligent about when to compile @import directives to plain CSS. Any of the following conditions will cause a literal CSS @import:

  • Importing a path with a .css extension (e.g. @import "foo.css").
  • Importing a path with a media type (e.g. @import "foo" screen;).
  • Importing an HTTP path (e.g. @import "http://foo.com/style.css").
  • Importing any URL (e.g. @import url(foo)).

The former two conditions always worked, but the latter two are new.

-moz-calc Support

The new -moz-calc() function in Firefox 4 will now be properly parsed by Sass. calc() was already supported, but because the parsing rules are different than for normal CSS functions, this had to be expanded to include -moz-calc.

In anticipation of wider browser support, in fact, any function named -*-calc (such as -webkit-calc or -ms-calc) will be parsed the same as the calc function.

:-moz-any Support

The :-moz-any pseudoclass selector is now parsed by Sass.

--require Flag

The Sass command-line executable can now require Ruby files using the --require flag (or -r for short).

Rails Support

Make sure the default Rails options take precedence over the default non-Rails options. This makes ./script/server --daemon work again.

Rails 3 Support

Support for Rails 3 versions prior to beta 4 has been removed. Upgrade to Rails 3.0.0.beta4 if you haven't already.

3.0.12

Tagged on GitHub.

Rails 3 Support

Apparently the last version broke in new and exciting ways under Rails 3, due to the inconsistent load order caused by certain combinations of gems. 3.0.12 hacks around that inconsistency, and should be fully Rails 3-compatible.

Deprecated: Rails 3 Beta 3

Haml's support for Rails 3.0.0.beta.3 has been deprecated. Haml 3.0.13 will only support 3.0.0.beta.4.

3.0.11

Tagged on GitHub.

There were no changes made to Haml between versions 3.0.10 and 3.0.11.

Rails 3 Support

Make sure Sass actually regenerates stylesheets under Rails 3. The fix in 3.0.10 didn't work because the Rack stack we were modifying wasn't reloaded at the proper time.

Bug Fixes

  • Give a decent error message when --recursive is used in sass-convert without a directory.

3.0.10

Tagged on GitHub.

Appengine-JRuby Support

The way we determine the location of the Haml installation no longer breaks the version of JRuby used by appengine-jruby.

Rails 3 Support

Sass will regenerate stylesheets under Rails 3 even when no controllers are being accessed.

Other Improvements

  • When using sass-convert --from sass2 --to sass --recursive, suggest the use of --in-place as well.

3.0.9

Tagged on GitHub.

There were no changes made to Sass between versions 3.0.8 and 3.0.9. A bug in Gemcutter caused the gem to be uploaded improperly.

3.0.8

Tagged on GitHub.

  • Fix a bug with Rails versions prior to Rails 3.

3.0.7

Tagged on GitHub.

Encoding Support

Sass 3.0.7 adds support for @charset for declaring the encoding of a stylesheet. For details see {file:SASS_REFERENCE.md#encodings the reference}.

The sass and sass-convert executables also now take an -E option for specifying the encoding of Sass/SCSS/CSS files.

Bug Fixes

  • When compiling a file named .sass but with SCSS syntax specified, use the latter (and vice versa).

  • Fix a bug where interpolation would cause some selectors to render improperly.

  • If a line in a Sass comment starts with *foo, render it as *foo rather than * *foo.

3.0.6

Tagged on GitHub.

There were no changes made to Sass between versions 3.0.5 and 3.0.6.

3.0.5

Tagged on GitHub.

#{} Interpolation in Properties

Previously, using #{} in some places in properties would cause a syntax error. Now it can be used just about anywhere.

Note that when #{} is used near operators like /, those operators are treated as plain CSS rather than math operators. For example:

p {
  $font-size: 12px;
  $line-height: 30px;
  font: #{$font-size}/#{$line-height};
}

is compiled to:

p {
  font: 12px/30px;
}

This is useful, since normally {file:SASS_REFERENCE.md#division-and-slash a slash with variables is treated as division}.

Recursive Mixins

Mixins that include themselves will now print much more informative error messages. For example:

@mixin foo {@include bar}
@mixin bar {@include foo}
@include foo

will print:

An @include loop has been found:
    foo includes bar
    bar includes foo

Although it was previously possible to use recursive mixins without causing infinite looping, this is now disallowed, since there's no good reason to do it.

Rails 3 Support

Fix Sass configuration under Rails 3. Thanks Dan Cheail.

sass --no-cache

Make the --no-cache flag properly forbid Sass from writing .sass-cache files.

3.0.4

Tagged on GitHub.

  • Raise an informative error when function arguments have a mispaced comma, as in foo(bar, ).

  • Fix a performance problem when using long function names such as -moz-linear-gradient.

3.0.3

Tagged on GitHub.

Rails 3 Support

Make sure Sass is loaded properly when using Rails 3 along with non-Rails-3-compatible plugins like some versions of will_paginate.

Also, In order to make some Rails loading errors like the above easier to debug, Sass will now raise an error if Rails.root is nil when Sass is loading. Previously, this would just cause the paths to be mis-set.

Merb Support

Merb, including 1.1.0 as well as earlier versions, should really work with this release.

Bug Fixes

  • Raise an informative error when mixin arguments have a mispaced comma, as in @include foo(bar, ).

  • Make sure SassScript subtraction happens even when nothing else dynamic is going on.

  • Raise an error when colors are used with the wrong number of digits.

3.0.2

Tagged on GitHub.

Merb 1.1.0 Support

Fixed a bug inserting the Sass plugin into the Merb 1.1.0 Rack application.

Bug Fixes

  • Allow identifiers to begin with multiple underscores.

  • Don't raise an error when using haml --rails with older Rails versions.

3.0.1

Tagged on GitHub.

Installation in Rails

haml --rails is no longer necessary for installing Sass in Rails. Now all you need to do is add gem "haml" to the Gemfile for Rails 3, or add config.gem "haml" to config/environment.rb for previous versions.

haml --rails will still work, but it has been deprecated and will print an error message. It will not work in the next version of Sass.

Rails 3 Beta Integration

  • Make sure manually importing the Sass Rack plugin still works with Rails, even though it's not necessary now.

  • Allow Sass to be configured in Rails even when it's being lazy-loaded.

:template_location Methods

The {file:SASS_REFERENCE.md#template_location-option :template_location option} can be either a String, a Hash, or an Array. This makes it difficult to modify or use with confidence. Thus, three new methods have been added for handling it:

  • {Sass::Plugin::Configuration#template_location_array Sass::Plugin#template_location_array} -- Returns the template locations and CSS locations formatted as an array.

  • {Sass::Plugin::Configuration#add_template_location Sass::Plugin#add_template_location} -- Converts the template location option to an array and adds a new location.

  • {Sass::Plugin::Configuration#remove_template_location Sass::Plugin#remove_template_location} -- Converts the template location option to an array and removes an existing location.

3.0.0

{#3-0-0}

Tagged on GitHub.

Deprecations -- Must Read!

{#3-0-0-deprecations}

  • Using = for SassScript properties and variables is deprecated, and will be removed in Sass 3.2. Use : instead. See also this changelog entry

  • Because of the above, property values using : will be parsed more thoroughly than they were before. Although all valid CSS3 properties as well as most hacks and proprietary syntax should be supported, it's possible that some properties will break. If this happens, please report it to the Sass mailing list.

  • In addition, setting the default value of variables with ||= is now deprecated and will be removed in Sass 3.2. Instead, add !default to the end of the value. See also this changelog entry

  • The ! prefix for variables is deprecated, and will be removed in Sass 3.2. Use $ as a prefix instead. See also this changelog entry.

  • The css2sass command-line tool has been deprecated, and will be removed in Sass 3.2. Use the new sass-convert tool instead. See also this changelog entry.

  • Selector parent references using & can now only be used where element names are valid. This is because Sass 3 fully parses selectors to support the new @extend directive, and it's possible that the & could be replaced by an element name.

SCSS (Sassy CSS)

Sass 3 introduces a new syntax known as SCSS which is fully compatible with the syntax of CSS3, while still supporting the full power of Sass. This means that every valid CSS3 stylesheet is a valid SCSS file with the same meaning. In addition, SCSS understands most CSS hacks and vendor-specific syntax, such as IE's old filter syntax.

SCSS files use the .scss extension. They can import .sass files, and vice-versa. Their syntax is fully described in the {file:SASS_REFERENCE.md Sass reference}; if you're already familiar with Sass, though, you may prefer the {file:SCSS_FOR_SASS_USERS.md intro to SCSS for Sass users}.

Since SCSS is a much more approachable syntax for those new to Sass, it will be used as the default syntax for the reference, as well as for most other Sass documentation. The indented syntax will continue to be fully supported, however.

Sass files can be converted to SCSS using the new sass-convert command-line tool. For example:

# Convert a Sass file to SCSS
$ sass-convert style.sass style.scss

Note that if you're converting a Sass file written for Sass 2, you should use the --from sass2 flag. For example:

# Convert a Sass file to SCSS
$ sass-convert --from sass2 style.sass style.scss

# Convert all Sass files to SCSS
$ sass-convert --recursive --in-place --from sass2 --to scss stylesheets/

Syntax Changes {#3-0-0-syntax-changes}

SassScript Context

{#3-0-0-sass-script-context}

The = character is no longer required for properties that use SassScript (that is, variables and operations). All properties now use SassScript automatically; this means that : should be used instead. Variables should also be set with :. For example, what used to be

// Indented syntax
.page
  color = 5px + 9px

should now be

// Indented syntax
.page
  color: 5px + 9px

This means that SassScript is now an extension of the CSS3 property syntax. All valid CSS3 properties are valid SassScript, and will compile without modification (some invalid properties work as well, such as Microsoft's proprietary filter syntax). This entails a few changes to SassScript to make it fully CSS3-compatible, which are detailed below.

This also means that Sass will now be fully parsing all property values, rather than passing them through unchanged to the CSS. Although care has been taken to support all valid CSS3, as well as hacks and proprietary syntax, it's possible that a property that worked in Sass 2 won't work in Sass 3. If this happens, please report it to the Sass mailing list.

Note that if = is used, SassScript will be interpreted as backwards-compatibly as posssible. In particular, the changes listed below don't apply in an = context.

The sass-convert command-line tool can be used to upgrade Sass files to the new syntax using the --in-place flag. For example:

# Upgrade style.sass:
$ sass-convert --in-place style.sass

# Upgrade all Sass files:
$ sass-convert --recursive --in-place --from sass2 --to sass stylesheets/
Quoted Strings

Quoted strings (e.g. "foo") in SassScript now render with quotes. In addition, unquoted strings are no longer deprecated, and render without quotes. This means that almost all strings that had quotes in Sass 2 should not have quotes in Sass 3.

Although quoted strings render with quotes when used with :, they do not render with quotes when used with #{}. This allows quoted strings to be used for e.g. selectors that are passed to mixins.

Strings can be forced to be quoted and unquoted using the new {Sass::Script::Functions#unquote unquote} and {Sass::Script::Functions#quote quote} functions.

Division and /

Two numbers separated by a / character are allowed as property syntax in CSS, e.g. for the font property. SassScript also uses / for division, however, which means it must decide what to do when it encounters numbers separated by /.

For CSS compatibility, SassScript does not perform division by default. However, division will be done in almost all cases where division is intended. In particular, SassScript will perform division in the following three situations:

  1. If the value, or any part of it, is stored in a variable.
  2. If the value is surrounded by parentheses.
  3. If the value is used as part of another arithmetic expression.

For example:

p
  font: 10px/8px
  $width: 1000px
  width: $width/2
  height: (500px/2)
  margin-left: 5px + 8px/2px

is compiled to:

p {
  font: 10px/8px;
  width: 500px;
  height: 250px;
  margin-left: 9px; }
Variable Defaults

Since = is no longer used for variable assignment, assigning defaults to variables with ||= no longer makes sense. Instead, the !default flag should be added to the end of the variable value. This syntax is meant to be similar to CSS's !important flag. For example:

$var: 12px !default;

Variable Prefix Character

{#3-0-0-dollar-prefix}

The Sass variable character has been changed from ! to the more aesthetically-appealing $. For example, what used to be

!width = 13px
.icon
  width = !width

should now be

$width: 13px
.icon
  width: $width

The sass-convert command-line tool can be used to upgrade Sass files to the new syntax using the --in-place flag. For example:

# Upgrade style.sass:
$ sass-convert --in-place style.sass

# Upgrade all Sass files:
$ sass-convert --recursive --in-place --from sass2 --to sass stylesheets/

! may still be used, but it's deprecated and will print a warning. It will be removed in the next version of Sass, 3.2.

Variable and Mixin Names

SassScript variable and mixin names may now contain hyphens. In fact, they may be any valid CSS3 identifier. For example:

$prettiest-color: #542FA9
=pretty-text
  color: $prettiest-color

In order to allow frameworks like Compass to use hyphens in variable names while maintaining backwards-compatibility, variables and mixins using hyphens may be referred to with underscores, and vice versa. For example:

$prettiest-color: #542FA9
.pretty
  // Using an underscore instead of a hyphen works
  color: $prettiest_color

Single-Quoted Strings

SassScript now supports single-quoted strings. They behave identically to double-quoted strings, except that single quotes need to be backslash-escaped and double quotes do not.

Mixin Definition and Inclusion

Sass now supports the @mixin directive as a way of defining mixins (like =), as well as the @include directive as a way of including them (like +). The old syntax is not deprecated, and the two are fully compatible. For example:

@mixin pretty-text
  color: $prettiest-color

a
  @include pretty-text

is the same as:

=pretty-text
  color: $prettiest-color

a
  +pretty-text

Sass Properties

New-style properties (with the colon after the name) in indented syntax now allow whitespace before the colon. For example:

foo
  color : blue

Sass @import

The Sass @import statement now allows non-CSS files to be specified with quotes, for similarity with the SCSS syntax. For example, @import "foo.sass" will now import the foo.sass file, rather than compiling to @import "foo.sass";.

@extend

{#3-0-0-extend}

There are often cases when designing a page when one class should have all the styles of another class, as well as its own specific styles. The most common way of handling this is to use both the more general class and the more specific class in the HTML. For example, suppose we have a design for a normal error and also for a serious error. We might write our markup like so:

<div class="error seriousError">
  Oh no! You've been hacked!
</div>

And our styles like so:

.error {
  border: 1px #f00;
  background-color: #fdd;
}
.seriousError {
  border-width: 3px;
}

Unfortunately, this means that we have to always remember to use .error with .seriousError. This is a maintenance burden, leads to tricky bugs, and can bring non-semantic style concerns into the markup.

The @extend directive avoids these problems by telling Sass that one selector should inherit the styles of another selector. For example:

.error {
  border: 1px #f00;
  background-color: #fdd;
}
.seriousError {
  @extend .error;
  border-width: 3px;
}

This means that all styles defined for .error are also applied to .seriousError, in addition to the styles specific to .seriousError. In effect, everything with class .seriousError also has class .error.

Other rules that use .error will work for .seriousError as well. For example, if we have special styles for errors caused by hackers:

.error.intrusion {
  background-image: url("/image/hacked.png");
}

Then <div class="seriousError intrusion"> will have the hacked.png background image as well.

How it Works

@extend works by inserting the extending selector (e.g. .seriousError) anywhere in the stylesheet that the extended selector (.e.g .error) appears. Thus the example above:

.error {
  border: 1px #f00;
  background-color: #fdd;
}
.error.intrusion {
  background-image: url("/image/hacked.png");
}
.seriousError {
  @extend .error;
  border-width: 3px;
}

is compiled to:

.error, .seriousError {
  border: 1px #f00;
  background-color: #fdd; }

.error.intrusion, .seriousError.intrusion {
  background-image: url("/image/hacked.png"); }

.seriousError {
  border-width: 3px; }

When merging selectors, @extend is smart enough to avoid unnecessary duplication, so something like .seriousError.seriousError gets translated to .seriousError. In addition, it won't produce selectors that can't match anything, like #main#footer.

See also {file:SASS_REFERENCE.md#extend the @extend reference documentation}.

Colors

SassScript color values are much more powerful than they were before. Support was added for alpha channels, and most of Chris Eppstein's compass-colors plugin was merged in, providing color-theoretic functions for modifying colors.

One of the most interesting of these functions is {Sass::Script::Functions#mix mix}, which mixes two colors together. This provides a much better way of combining colors and creating themes than standard color arithmetic.

Alpha Channels

Sass now supports colors with alpha channels, constructed via the {Sass::Script::Functions#rgba rgba} and {Sass::Script::Functions#hsla hsla} functions. Alpha channels are unaffected by color arithmetic. However, the {Sass::Script::Functions#opacify opacify} and {Sass::Script::Functions#transparentize transparentize} functions allow colors to be made more and less opaque, respectively.

Sass now also supports functions that return the values of the {Sass::Script::Functions#red red}, {Sass::Script::Functions#blue blue}, {Sass::Script::Functions#green green}, and {Sass::Script::Functions#alpha alpha} components of colors.

HSL Colors

Sass has many new functions for using the HSL values of colors. For an overview of HSL colors, check out the CSS3 Spec. All these functions work just as well on RGB colors as on colors constructed with the {Sass::Script::Functions#hsl hsl} function.

  • The {Sass::Script::Functions#lighten lighten} and {Sass::Script::Functions#darken darken} functions adjust the lightness of a color.

  • The {Sass::Script::Functions#saturate saturate} and {Sass::Script::Functions#desaturate desaturate} functions adjust the saturation of a color.

  • The {Sass::Script::Functions#adjust_hue adjust-hue} function adjusts the hue of a color.

  • The {Sass::Script::Functions#hue hue}, {Sass::Script::Functions#saturation saturation}, and {Sass::Script::Functions#lightness lightness} functions return the corresponding HSL values of the color.

  • The {Sass::Script::Functions#grayscale grayscale} function converts a color to grayscale.

  • The {Sass::Script::Functions#complement complement} function returns the complement of a color.

Other New Functions

Several other new functions were added to make it easier to have more flexible arguments to mixins and to enable deprecation of obsolete APIs.

  • {Sass::Script::Functions#type_of type-of} -- Returns the type of a value.
  • {Sass::Script::Functions#unit unit} -- Returns the units associated with a number.
  • {Sass::Script::Functions#unitless unitless} -- Returns whether a number has units or not.
  • {Sass::Script::Functions#comparable comparable} -- Returns whether two numbers can be added or compared.

Watching for Updates

{#3-0-0-watch}

The sass command-line utility has a new flag: --watch. sass --watch monitors files or directories for updated Sass files and compiles those files to CSS automatically. This will allow people not using Ruby or Compass to use Sass without having to manually recompile all the time.

Here's the syntax for watching a directory full of Sass files:

sass --watch app/stylesheets:public/stylesheets

This will watch every Sass file in app/stylesheets. Whenever one of them changes, the corresponding CSS file in public/stylesheets will be regenerated. Any files that import that file will be regenerated, too.

The syntax for watching individual files is the same:

sass --watch style.sass:out.css

You can also omit the output filename if you just want it to compile to name.css. For example:

sass --watch style.sass

This will update style.css whenever style.sass changes.

You can list more than one file and/or directory, and all of them will be watched:

sass --watch foo/style:public/foo bar/style:public/bar
sass --watch screen.sass print.sass awful-hacks.sass:ie.css
sass --watch app/stylesheets:public/stylesheets public/stylesheets/test.sass

File and directory watching is accessible from Ruby, using the {Sass::Plugin::Compiler#watch Sass::Plugin#watch} function.

Bulk Updating

Another new flag for the sass command-line utility is --update. It checks a group of Sass files to see if their CSS needs to be updated, and updates if so.

The syntax for --update is just like watch:

sass --update app/stylesheets:public/stylesheets
sass --update style.sass:out.css
sass --watch screen.sass print.sass awful-hacks.sass:ie.css

In fact, --update work exactly the same as --watch, except that it doesn't continue watching the files after the first check.

sass-convert (née css2sass) {#3-0-0-sass-convert}

The sass-convert tool, which used to be known as css2sass, has been greatly improved in various ways. It now uses a full-fledged CSS3 parser, so it should be able to handle any valid CSS3, as well as most hacks and proprietary syntax.

sass-convert can now convert between Sass and SCSS. This is normally inferred from the filename, but it can also be specified using the --from and --to flags. For example:

$ generate-sass | sass-convert --from sass --to scss | consume-scss

It's also now possible to convert a file in-place -- that is, overwrite the old file with the new file. This is useful for converting files in the Sass 2 syntax to the new Sass 3 syntax, e.g. by doing sass-convert --in-place --from sass2 style.sass.

--recursive

The --recursive option allows sass-convert to convert an entire directory of files. --recursive requires both the --from and --to flags to be specified. For example:

# Convert all .sass files in stylesheets/ to SCSS.
# "sass2" means that these files are assumed to use the Sass 2 syntax.
$ sass-convert --recursive --from sass2 --to scss stylesheets/

--dasherize

The --dasherize options converts all underscores to hyphens, which are now allowed as part of identifiers in Sass. Note that since underscores may still be used in place of hyphens when referring to mixins and variables, this won't cause any backwards-incompatibilities.

Convert Less to SCSS

sass-convert can also convert Less files to SCSS (or the indented syntax, although I anticipate less interest in that). For example:

# Convert all .less files in the current directory into .scss files
sass-convert --from less --to scss --recursive .

This is done using the Less parser, so it requires that the less RubyGem be installed.

Incompatibilities

Because of the reasonably substantial differences between Sass and Less, there are some things that can't be directly translated, and one feature that can't be translated at all. In the tests I've run on open-source Less stylesheets, none of these have presented issues, but it's good to be aware of them.

First, Less doesn't distinguish fully between mixins and selector inheritance. In Less, all classes and some other selectors may be used as mixins, alongside more Sass-like mixins. If a class is being used as a mixin, it may also be used directly in the HTML, so it's not safe to translate it into a Sass mixin. What sass-convert does instead is leave the class in the stylesheet as a class, and use {file:SASS_REFERENCE.md#extend @extend} rather than {file:SASS_REFERENCE.md#including_a_mixin @include} to take on the styles of that class. Although @extend and mixins work quite differently, using @extend here doesn't actually seem to make a difference in practice.

Another issue with Less mixins is that Less allows nested selectors (such as .body .button or .colors > .teal) to be used as a means of "namespacing" mixins. Sass's @extend doesn't work that way, so it does away with the namespacing and just extends the base class (so .colors > .teal becomes simply @extend .teal). In practice, this feature doesn't seem to be widely-used, but sass-convert will print a warning and leave a comment when it encounters it just in case.

Finally, Less has the ability to directly access variables and property values defined in other selectors, which Sass does not support. Whenever such an accessor is used, sass-convert will print a warning and comment it out in the SCSS output. Like namespaced mixins, though, this does not seem to be a widely-used feature.

@warn Directive

A new directive @warn has been added that allows Sass libraries to emit warnings. This can be used to issue deprecation warnings, discourage sloppy use of mixins, etc. @warn takes a single argument: a SassScript expression that will be displayed on the console along with a stylesheet trace for locating the warning. For example:

@mixin blue-text {
  @warn "The blue-text mixin is deprecated. Use new-blue-text instead.";
  color: #00f;
}

Warnings may be silenced with the new --quiet command line option, or the corresponding {file:SASS_REFERENCE.md#quiet-option :quiey Sass option}. This option will also affect warnings printed by Sass itself. Warnings are off by default in the Rails, Rack, and Merb production environments.

Sass::Plugin API

{Sass::Plugin} now has a large collection of callbacks that allow users to run code when various actions are performed. For example:

Sass::Plugin.on_updating_stylesheet do |template, css|
  puts "#{template} has been compiled to #{css}!"
end

For a full list of callbacks and usage notes, see the {Sass::Plugin} documentation.

{Sass::Plugin} also has a new method, {Sass::Plugin#force_update_stylesheets force_update_stylesheets}. This works just like {Sass::Plugin#update_stylesheets}, except that it doesn't check modification times and doesn't use the cache; all stylesheets are always compiled anew.

Output Formatting

Properties with a value and also nested properties are now rendered with the nested properties indented. For example:

margin: auto
  top: 10px
  bottom: 20px

is now compiled to:

margin: auto;
  margin-top: 10px;
  margin-bottom: 20px;

:compressed Style

When the :compressed style is used, colors will be output as the minimal possible representation. This means whichever is smallest of the HTML4 color name and the hex representation (shortened to the three-letter version if possible).

Stylesheet Updating Speed

Several caching layers were added to Sass's stylesheet updater. This means that it should run significantly faster. This benefit will be seen by people using Sass in development mode with Rails, Rack, and Merb, as well as people using sass --watch from the command line, and to a lesser (but still significant) extent sass --update. Thanks to thedarkone.

Error Backtraces

Numerous bugs were fixed with the backtraces given for Sass errors, especially when importing files and using mixins. All imports and mixins will now show up in the Ruby backtrace, with the proper filename and line number.

In addition, when the sass executable encounters an error, it now prints the filename where the error occurs, as well as a backtrace of Sass imports and mixins.

Ruby 1.9 Support

  • Sass and css2sass now produce more descriptive errors when given a template with invalid byte sequences for that template's encoding, including the line number and the offending character.

  • Sass and css2sass now accept Unicode documents with a byte-order-mark.

Firebug Support

A new {file:SASS_REFERENCE.md#debug_info-option :debug_info option} has been added that emits line-number and filename information to the CSS file in a browser-readable format. This can be used with the new FireSass Firebug extension to report the Sass filename and line number for generated CSS files.

This is also available via the --debug-info command-line flag.

Minor Improvements

  • If a CSS or Sass function is used that has the name of a color, it will now be parsed as a function rather than as a color. For example, fuchsia(12) now renders as fuchsia(12) rather than fuchsia 12, and tealbang(12) now renders as tealbang(12) rather than teal bang(12).

  • The Sass Rails and Merb plugins now use Rack middleware by default.

  • Haml is now compatible with the Rip package management system. Thanks to Josh Peek.

  • Indented-syntax /* comments may now include * on lines beyond the first.

  • A {file:SASS_REFERENCE.md#read_cache-option :read_cache} option has been added to allow the Sass cache to be read from but not written to.

  • Stylesheets are no longer checked during each request when running tests in Rails. This should speed up some tests significantly.

2.2.24

Tagged on GitHub.

  • Parent references -- the & character -- may only be placed at the beginning of simple selector sequences in Sass 3. Placing them elsewhere is deprecated in 2.2.24 and will print a warning. For example, foo &.bar is allowed, but foo .bar& is not.

2.2.23

Tagged on GitHub.

  • Don't crash when rake gems is run in Rails with Sass installed. Thanks to Florian Frank.

  • When raising a file-not-found error, add a list of load paths that were checked.

  • If an import isn't found for a cached Sass file and the {file:SASS_REFERENCE.md#full_exception :full_exception option} is enabled, print the full exception rather than raising it.

  • Fix a bug with a weird interaction with Haml, DataMapper, and Rails 3 that caused some tag helpers to go into infinite recursion.

2.2.22

Tagged on GitHub.

  • Add a railtie so Haml and Sass will be automatically loaded in Rails 3. Thanks to Daniel Neighman.

  • Make loading the gemspec not crash on read-only filesystems like Heroku's.

2.2.21

Tagged on GitHub.

  • Fix a few bugs in the git-revision-reporting in {Sass::Version#version}. In particular, it will still work if git gc has been called recently, or if various files are missing.

  • Always use __FILE__ when reading files within the Haml repo in the Rakefile. According to this bug report, this should make Sass work better with Bundler.

2.2.20

Tagged on GitHub.

  • If the cache file for a given Sass file is corrupt because it doesn't have enough content, produce a warning and read the Sass file rather than letting the exception bubble up. This is consistent with other sorts of sassc corruption handling.

  • Calls to defined? shouldn't interfere with Rails' autoloading in very old versions (1.2.x).

2.2.19

Tagged on GitHub.

There were no changes made to Sass between versions 2.2.18 and 2.2.19.

2.2.18

Tagged on GitHub.

  • Use Rails.env rather than RAILS_ENV when running under Rails 3.0. Thanks to Duncan Grazier.

  • Support :line_numbers as an alias for {file:SASS_REFERENCE.md#line_numbers-option :line_comments}, since that's what the docs have said forever. Similarly, support --line-numbers as a command-line option.

  • Add a --unix-newlines flag to all executables for outputting Unix-style newlines on Windows.

  • Add a {file:SASS_REFERENCE.md#unix_newlines-option :unix_newlines option} for {Sass::Plugin} for outputting Unix-style newlines on Windows.

  • Fix the --cache-location flag, which was previously throwing errors. Thanks to tav.

  • Allow comments at the beginning of the document to have arbitrary indentation, just like comments elsewhere. Similarly, comment parsing is a little nicer than before.

2.2.17

Tagged on GitHub.

  • When the {file:SASS_REFERENCE.md#full_exception-option :full_exception option} is false, raise the error in Ruby code rather than swallowing it and printing something uninformative.

  • Fixed error-reporting when something goes wrong when loading Sass using the sass executable. This used to raise a NameError because Sass::SyntaxError wasn't defined. Now it'll raise the correct exception instead.

  • Report the filename in warnings about selectors without properties.

  • nil values for Sass options are now ignored, rather than raising errors.

  • Fix a bug that appears when Plugin template locations have multiple trailing slashes. Thanks to Jared Grippe.

Must Read!

  • When @import is given a filename without an extension, the behavior of rendering a CSS @import if no Sass file is found is deprecated. In future versions, @import foo will either import the template or raise an error.

2.2.16

Tagged on GitHub.

  • Fixed a bug where modules containing user-defined Sass functions weren't made available when simply included in {Sass::Script::Functions} ({Sass::Script::Functions Functions} needed to be re-included in {Sass::Script::Functions::EvaluationContext Functions::EvaluationContext}). Now the module simply needs to be included in {Sass::Script::Functions}.

2.2.15

Tagged on GitHub.

  • Added {Sass::Script::Color#with} for a way of setting color channels that's easier than manually constructing a new color and is forwards-compatible with alpha-channel colors (to be introduced in Sass 2.4).

  • Added a missing require in Sass that caused crashes when it was being run standalone.

2.2.14

Tagged on GitHub.

  • All Sass functions now raise explicit errors if their inputs are of the incorrect type.

  • Allow the SassScript rgb() function to take percentages in addition to numerical values.

  • Fixed a bug where SassScript strings with # followed by #{} interpolation didn't evaluate the interpolation.

SassScript Ruby API

These changes only affect people defining their own Sass functions using {Sass::Script::Functions}.

  • Sass::Script::Color#value attribute is deprecated. Use {Sass::Script::Color#rgb} instead. The returned array is now frozen as well.

  • Add an assert_type function that's available to {Sass::Script::Functions}. This is useful for typechecking the inputs to functions.

Rack Support

Sass 2.2.14 includes Rack middleware for running Sass, meaning that all Rack-enabled frameworks can now use Sass. To activate this, just add

require 'sass/plugin/rack'
use Sass::Plugin::Rack

to your config.ru. See the {Sass::Plugin::Rack} documentation for more details.

2.2.13

Tagged on GitHub.

There were no changes made to Sass between versions 2.2.12 and 2.2.13.

2.2.12

Tagged on GitHub.

  • Fix a stupid bug introduced in 2.2.11 that broke the Sass Rails plugin.

2.2.11

Tagged on GitHub.

  • Added a note to errors on properties that could be pseudo-classes (e.g. :focus) indicating that they should be backslash-escaped.

  • Automatically interpret properties that could be pseudo-classes as such if {file:SASS_REFERENCE.md.html#property_syntax-option :property_syntax} is set to :new.

  • Fixed css2sass's generation of pseudo-classes so that they're backslash-escaped.

  • Don't crash if the Haml plugin skeleton is installed and rake gems:install is run.

  • Don't use RAILS_ROOT directly. This no longer exists in Rails 3.0. Instead abstract this out as Haml::Util.rails_root. This changes makes Haml fully compatible with edge Rails as of this writing.

  • Make use of a Rails callback rather than a monkeypatch to check for stylesheet updates in Rails 3.0+.

2.2.10

Tagged on GitHub.

  • Add support for attribute selectors with spaces around the =. For example:

    a[href = http://google.com]
  color: blue

2.2.9

Tagged on GitHub.

There were no changes made to Sass between versions 2.2.8 and 2.2.9.

2.2.8

Tagged on GitHub.

There were no changes made to Sass between versions 2.2.7 and 2.2.8.

2.2.7

Tagged on GitHub.

There were no changes made to Sass between versions 2.2.6 and 2.2.7.

2.2.6

Tagged on GitHub.

  • Don't crash when the __FILE__ constant of a Ruby file is a relative path, as apparently happens sometimes in TextMate (thanks to Karl Varga).

  • Add "Sass" to the --version string for the executables.

2.2.5

Tagged on GitHub.

There were no changes made to Sass between versions 2.2.4 and 2.2.5.

2.2.4

Tagged on GitHub.

  • Don't add require 'rubygems' to the top of init.rb when installed via sass --rails. This isn't necessary, and actually gets clobbered as soon as haml/template is loaded.

  • Document the previously-undocumented {file:SASS_REFERENCE.md#line-option :line option}, which allows the number of the first line of a Sass file to be set for error reporting.

2.2.3

Tagged on GitHub.

Sass 2.2.3 prints line numbers for warnings about selectors with no properties.

2.2.2

Tagged on GitHub.

Sass 2.2.2 is a minor bug-fix release. Notable changes include better parsing of mixin definitions and inclusions and better support for Ruby 1.9.

2.2.1

Tagged on GitHub.

Sass 2.2.1 is a minor bug-fix release.

Must Read!

  • It used to be acceptable to use - immediately following variable names, without any whitespace in between (for example, !foo-!bar). This is now deprecated, so that in the future variables with hyphens can be supported. Surround - with spaces.

2.2.0

Tagged on GitHub.

The 2.2 release marks a significant step in the evolution of the Sass language. The focus has been to increase the power of Sass to keep your stylesheets maintainable by allowing new forms of abstraction to be created within your stylesheets and the stylesheets provided by others that you can download and import into your own. The fundamental units of abstraction in Sass are variables and mixins. Please read below for a list of changes:

Must Read!

  • Sass Comments (//) used to only comment out a single line. This was deprecated in 2.0.10 and starting in 2.2, Sass comments will comment out any lines indented under them. Upgrade to 2.0.10 in order to see deprecation warnings where this change affects you.

  • Implicit Strings within SassScript are now deprecated and will be removed in 2.4. For example: border= !width solid #00F should now be written as border: #{!width} solid #00F or as border= !width "solid" #00F. After upgrading to 2.2, you will see deprecation warnings if you have sass files that use implicit strings.

Sass Syntax Changes

Flexible Indentation

The indentation of Sass documents is now flexible. The first indent that is detected will determine the indentation style for that document. Tabs and spaces may never be mixed, but within a document, you may choose to use tabs or a flexible number of spaces.

Multiline Sass Comments

Sass Comments (//) will now comment out whatever is indented beneath them. Previously they were single line when used at the top level of a document. Upgrading to the latest stable version will give you deprecation warnings if you have silent comments with indentation underneath them.

Mixin Arguments

Sass Mixins now accept any number of arguments. To define a mixin with arguments, specify the arguments as a comma-delimited list of variables like so:

=my-mixin(!arg1, !arg2, !arg3)

As before, the definition of the mixin is indented below the mixin declaration. The variables declared in the argument list may be used and will be bound to the values passed to the mixin when it is invoked. Trailing arguments may have default values as part of the declaration:

=my-mixin(!arg1, !arg2 = 1px, !arg3 = blue)

In the example above, the mixin may be invoked by passing 1, 2 or 3 arguments to it. A similar syntax is used to invoke a mixin that accepts arguments:

div.foo
  +my-mixin(1em, 3px)

When a mixin has no required arguments, the parenthesis are optional.

The default values for mixin arguments are evaluated in the global context at the time when the mixin is invoked, they may also reference the previous arguments in the declaration. For example:

!default_width = 30px
=my-fancy-mixin(!width = !default_width, !height = !width)
  width= !width
  height= !height

.default-box
  +my-fancy-mixin

.square-box
  +my-fancy-mixin(50px)

.rectangle-box
  +my-fancy-mixin(25px, 75px)

!default_width = 10px
.small-default-box
  +my-fancy-mixin

compiles to:

.default-box {
  width: 30px;
  height: 30px; }

.square-box {
  width: 50px;
  height: 50px; }

.rectangle-box {
  width: 25px;
  height: 75px; }

.small-default-box {
  width: 10px;
  height: 10px; }

Sass, Interactive

The sass command line option -i now allows you to quickly and interactively experiment with SassScript expressions. The value of the expression you enter will be printed out after each line. Example:

$ sass -i
>> 5px
5px
>> 5px + 10px
15px
>> !five_pixels = 5px
5px
>> !five_pixels + 10px
15px

SassScript

The features of SassScript have been greatly enhanced with new control directives, new fundamental data types, and variable scoping.

New Data Types

SassScript now has four fundamental data types:

  1. Number
  2. String
  3. Boolean (New in 2.2)
  4. Colors

More Flexible Numbers

Like JavaScript, SassScript numbers can now change between floating point and integers. No explicit casting or decimal syntax is required. When a number is emitted into a CSS file it will be rounded to the nearest thousandth, however the internal representation maintains much higher precision.

Improved Handling of Units

While Sass has long supported numbers with units, it now has a much deeper understanding of them. The following are examples of legal numbers in SassScript:

0, 1000, 6%, -2px, 5pc, 20em, or 2foo.

Numbers of the same unit may always be added and subtracted. Numbers that have units that Sass understands and finds comparable, can be combined, taking the unit of the first number. Numbers that have non-comparable units may not be added nor subtracted -- any attempt to do so will cause an error. However, a unitless number takes on the unit of the other number during a mathematical operation. For example:

>> 3mm + 4cm
43mm
>> 4cm + 3mm
4.3cm
>> 3cm + 2in
8.08cm
>> 5foo + 6foo
11foo
>> 4% + 5px
SyntaxError: Incompatible units: 'px' and '%'.
>> 5 + 10px
15px

Sass allows compound units to be stored in any intermediate form, but will raise an error if you try to emit a compound unit into your css file.

>> !em_ratio = 1em / 16px
0.063em/px
>> !em_ratio * 32px
2em
>> !em_ratio * 40px
2.5em

Colors

A color value can be declared using a color name, hexadecimal, shorthand hexadecimal, the rgb function, or the hsl function. When outputting a color into css, the color name is used, if any, otherwise it is emitted as hexadecimal value. Examples:

> #fff
white
>> white
white
>> #FFFFFF
white
>> hsl(180, 100, 100)
white
>> rgb(255, 255, 255)
white
>> #AAA
#aaaaaa

Math on color objects is performed piecewise on the rgb components. However, these operations rarely have meaning in the design domain (mostly they make sense for gray-scale colors).

>> #aaa + #123
#bbccdd
>> #333 * 2
#666666

Booleans

Boolean objects can be created by comparison operators or via the true and false keywords. Booleans can be combined using the and, or, and not keywords.

>> true
true
>> true and false
false
>> 5 < 10
true
>> not (5 < 10)
false
>> not (5 < 10) or not (10 < 5)
true
>> 30mm == 3cm
true
>> 1px == 1em
false

Strings

Unicode escapes are now allowed within SassScript strings.

Control Directives

New directives provide branching and looping within a sass stylesheet based on SassScript expressions. See the Sass Reference for complete details.

@for

The @for directive loops over a set of numbers in sequence, defining the current number into the variable specified for each loop. The through keyword means that the last iteration will include the number, the to keyword means that it will stop just before that number.

@for !x from 1px through 5px
  .border-#{!x}
    border-width= !x

compiles to:

.border-1px {
  border-width: 1px; }

.border-2px {
  border-width: 2px; }

.border-3px {
  border-width: 3px; }

.border-4px {
  border-width: 4px; }

.border-5px {
  border-width: 5px; }

@if / @else if / @else

The branching directives @if, @else if, and @else let you select between several branches of sass to be emitted, based on the result of a SassScript expression. Example:

!type = "monster"
p
  @if !type == "ocean"
    color: blue
  @else if !type == "matador"
    color: red
  @else if !type == "monster"
    color: green
  @else
    color: black

is compiled to:

p {
  color: green; }

@while

The @while directive lets you iterate until a condition is met. Example:

!i = 6
@while !i > 0
  .item-#{!i}
    width = 2em * !i
  !i = !i - 2

is compiled to:

.item-6 {
  width: 12em; }

.item-4 {
  width: 8em; }

.item-2 {
  width: 4em; }

Variable Scoping

The term "constant" has been renamed to "variable." Variables can be declared at any scope (a.k.a. nesting level) and they will only be visible to the code until the next outdent. However, if a variable is already defined in a higher level scope, setting it will overwrite the value stored previously.

In this code, the !local_var variable is scoped and hidden from other higher level scopes or sibling scopes:

.foo
  .bar
    !local_var = 1px
    width= !local_var
  .baz
    // this will raise an undefined variable error.
    width= !local_var
  // as will this
  width= !local_var

In this example, since the !global_var variable is first declared at a higher scope, it is shared among all lower scopes:

!global_var = 1px
.foo
  .bar
    !global_var = 2px
    width= !global_var
  .baz
    width= !global_var
  width= !global_var

compiles to:

.foo {
  width: 2px; }
  .foo .bar {
    width: 2px; }
  .foo .baz {
    width: 2px; }

Interpolation

Interpolation has been added. This allows SassScript to be used to create dynamic properties and selectors. It also cleans up some uses of dynamic values when dealing with compound properties. Using interpolation, the result of a SassScript expression can be placed anywhere:

!x = 1
!d = 3
!property = "border"
div.#{!property}
  #{!property}: #{!x + !d}px solid
  #{!property}-color: blue

is compiled to:

div.border {
  border: 4px solid;
  border-color: blue; }

Sass Functions

SassScript defines some useful functions that are called using the normal CSS function syntax:

p
  color = hsl(0, 100%, 50%)

is compiled to:

#main {
  color: #ff0000; }

The following functions are provided: hsl, percentage, round, ceil, floor, and abs. You can define additional functions in ruby.

See {Sass::Script::Functions} for more information.

New Options

:line_comments

To aid in debugging, You may set the :line_comments option to true. This will cause the sass engine to insert a comment before each selector saying where that selector was defined in your sass code.

:template_location

The {Sass::Plugin} :template_location option now accepts a hash of sass paths to corresponding css paths. Please be aware that it is possible to import sass files between these separate locations -- they are not isolated from each other.

Miscellaneous Features

@debug Directive

The @debug directive accepts a SassScript expression and emits the value of that expression to the terminal (stderr).

Example:

@debug 1px + 2px

During compilation the following will be printed:

Line 1 DEBUG: 3px

Ruby 1.9 Support

Sass now fully supports Ruby 1.9.1.

Sass Cache

By default, Sass caches compiled templates and partials. This dramatically speeds up re-compilation of large collections of Sass files, and works best if the Sass templates are split up into separate files that are all @imported into one large file.

Without a framework, Sass puts the cached templates in the .sass-cache directory. In Rails and Merb, they go in tmp/sass-cache. The directory can be customized with the :cache_location option. If you don't want Sass to use caching at all, set the :cache option to false.