Escaped characters in CSS content are not respected #133
Comments
|
@andreypopp @JackVCurtis @mathieumg are any of you still able to reproduce this issue? |
|
I have no idea why this worked but putting |
|
Ok, nevermind, that does NOT work. |
|
|
|
Any word on this? I hate keeping this lib at |
|
@chandlervdw my workaround was to alter content value to work with
|
|
@robmcguinness I'm trying to achieve an end value of |
|
@chandlervdw I haven't dug into the code in a while but if I get a minute i'll take a peek |
|
Traced the problem to css-modules/css-selector-tokenizer#12 |
This fixes the parsing of unicode strings that are 1 or 6 hex characters long. Extends the tests to support a third element in examples, which would be the re-stringified example, since a unicode character might be stringified in a different way than the original code, and still be valid. fixes webpack-contrib/css-loader#133 fixes css-modules#12
This fixes the parsing of unicode strings that are 1 or 6 hex characters long. Extends the tests to support a third element in examples, which would be the re-stringified example, since a unicode character might be stringified in a different way than the original code, and still be valid. fixes webpack-contrib/css-loader#133 fixes css-modules#12
|
+1 |
|
hi guys, encountering same issue, any tweak i should do to make it work for now? |
|
Added a PR to bump the |
Even though this was listed in #87 and supposedly fixed by css-modules/css-selector-tokenizer@5aa6180, I'm still having this issue.
content: "\A";is compiled tocontent: "A";, so the\character isn't being parsed correctly...The text was updated successfully, but these errors were encountered: