You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how valid this is in CSS, but I feel like both of these should produce the same result and that curly brackets position should not affect compiler result. Also using Sass 3.4.14 compiler both SCSS variations are compiled into the same result, with the whole selector being on the same line. Using output style nested produces similar results.
All these steps are reproduceable in http://sassmeister.com/. Use the gear-button to change compilers.
The text was updated successfully, but these errors were encountered:
Thanks @gligoran you're correct the output should be the same in both case. The output CSS is valid and semantically equivalent so this is a low priority bug for the time being.
mgreter
added a commit
to mgreter/sass-spec
that referenced
this issue
Aug 24, 2015
For example, when the open curly brackets are in the same line as the selector:
libSass produces this:
But is you put the curly brackets in their own line:
you get this:
I'm not sure how valid this is in CSS, but I feel like both of these should produce the same result and that curly brackets position should not affect compiler result. Also using Sass 3.4.14 compiler both SCSS variations are compiled into the same result, with the whole selector being on the same line. Using output style nested produces similar results.
All these steps are reproduceable in http://sassmeister.com/. Use the gear-button to change compilers.
The text was updated successfully, but these errors were encountered: