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
becomes : div#download:before{display:block;content:"T\E9l\E9 charger le fichier YAML";text-align:center}
with two spaces after the unicode declaration which will display in the final page as "télé charger" instead of "télécharger"
I tried variations of it to see if I was missing something:
content:"T\E9l\E9charger"; => content:"T\E9l\E9Charger" =>" tél(accentued greek omega)harger"
content:"T\E9l\E9 charger"; => content:"T\E9l\E9 charger" with three spaces=> "télé charger"
content:"T\E9l\E9\000063harger"; => content:"T\E9l\E9 charger"; with two spaces => "télé charger"
content:"T\E9l\0000E9\000063harger"; => content:"T\E9l\E9 charger"; with two spaces => "télé charger"
What is the expected behavior?
the expected behavior would be to transform content:"T\E9l\0000E9charger";
in content:"T\E9l\E9 charger";
with only one space (to escape the unicode recognition, but not 2 as it is now that add an extra space in the final HTML render.
Please mention other relevant information such as your webpack version, Node.js version and Operating System.
I use
yes and no I think, this fail as well on the full unicode \0000E9, so unless this gets executed twice (from "\0000E9" to "\E9 " (with one space) then to "\E9 " (with two spaces), that shouldn't happen.
hi
Do you want to request a feature or report a bug?
bug
I encounter a problem with how css-loader handle unicode in my CSS file
What is the current behavior?
When i feed the unicode for "é" : \0000E9, the compiled css ends up being mimified but transformed so
becomes :
div#download:before{display:block;content:"T\E9l\E9 charger le fichier YAML";text-align:center}
with two spaces after the unicode declaration which will display in the final page as "télé charger" instead of "télécharger"
I tried variations of it to see if I was missing something:
content:"T\E9l\E9charger"; => content:"T\E9l\E9Charger" =>" tél(accentued greek omega)harger"
content:"T\E9l\E9 charger"; => content:"T\E9l\E9 charger" with three spaces=> "télé charger"
content:"T\E9l\E9\000063harger"; => content:"T\E9l\E9 charger"; with two spaces => "télé charger"
content:"T\E9l\0000E9\000063harger"; => content:"T\E9l\E9 charger"; with two spaces => "télé charger"
What is the expected behavior?
the expected behavior would be to transform
content:"T\E9l\0000E9charger";
in
content:"T\E9l\E9 charger";
with only one space (to escape the unicode recognition, but not 2 as it is now that add an extra space in the final HTML render.
Please mention other relevant information such as your webpack version, Node.js version and Operating System.
I use
and my rule for match css is
thanks
The text was updated successfully, but these errors were encountered: