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.

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

Error parsing selector with escaped colon at the end #2625

Closed
jsdw opened this issue Mar 29, 2018 · 2 comments
Closed

Error parsing selector with escaped colon at the end #2625

jsdw opened this issue Mar 29, 2018 · 2 comments
Assignees

Comments

@jsdw
Copy link

jsdw commented Mar 29, 2018

Using libsass 3.5.2 (via node-sass 4.8.3), The following leads to an error:

$ echo -e 'something\:{ padding: 2px; }' | ./node-sass
{
  "status": 1,
  "file": "stdin",
  "line": 1,
  "column": 1,
  "message": "Invalid CSS after \"s\": expected 1 selector or at-rule, was \"something\\\\:{ paddin\"",
  "formatted": "Error: Invalid CSS after \"s\": expected 1 selector or at-rule, was \"something\\\\:{ paddin\"\n        on line 1 of stdin\n>> something\\:{ padding: 2px; }\n\n   ^\n"
}

Adding a space between the colon and opening curly bracket works, eg:

$ echo -e 'something\: { padding: 2px; }' | ./node-sass
something\: {
  padding: 2px; }

This is a regression, and does not appear to be a problem using libsass 3.5.0.beta.2 (via node-sass 4.5.3).

@xzyfer
Copy link
Contributor

xzyfer commented Mar 29, 2018 via email

@xzyfer
Copy link
Contributor

xzyfer commented Mar 30, 2018

Confirmed this is a regression in 3.5.0.

xzyfer added a commit to xzyfer/sass-spec that referenced this issue Mar 30, 2018
xzyfer added a commit to xzyfer/libsass that referenced this issue Mar 30, 2018
xzyfer added a commit to xzyfer/libsass that referenced this issue Mar 30, 2018
xzyfer added a commit to sass/sass-spec that referenced this issue Mar 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants