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
This is a minor issue, but a Lucius rule like this:
li {
content: ";";
}
will give an error message like this:
(line 365, column 2):
unexpected end of input
expecting "/*", "}", "#", "@" or "{"
checkIfBlock
where the error message doesn't occur until the last line.
The parser doesn't seem to recognize that the semicolon is quoted. I tried "\;" but that has no effect. I believe CSS allows semicolons in strings and also allows backslash escaping (http://www.w3.org/TR/CSS2/syndata.html#characters).
I am using Shakespeare version shakespeare-0.10.3.1.
The text was updated successfully, but these errors were encountered:
Sorry for the delay in responding to this, it slipped between the cracks.
Unfortunately, it's a bit more complicated in Lucius, since it's entirely possible to include the close quote in a variable interpolation, e.g.:
li {
content: ";#{quote};
}
Maybe we want to say that's a ridiculous case that should be ignored, but that's a decision we need to make since doing so could in theory break code. (It probably has larger effects than just this degenerate case.)
As a temporary workaround, you can do something like this:
This is a minor issue, but a Lucius rule like this:
will give an error message like this:
where the error message doesn't occur until the last line.
The parser doesn't seem to recognize that the semicolon is quoted. I tried
"\;"
but that has no effect. I believe CSS allows semicolons in strings and also allows backslash escaping (http://www.w3.org/TR/CSS2/syndata.html#characters).I am using Shakespeare version shakespeare-0.10.3.1.
The text was updated successfully, but these errors were encountered: