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
Describe the bug
When decompiling a file (using -d option) and it contains pseudo elements in CSS like ::-webkit-scrollbar, the resulting file cannot be recompiled as the pseudo element is taken as the name of a passage, if the pseudo-element is at the beginning of a line.
Expected behavior
I would expect that decompiling and then recompiling any file without modifying it should work.
Desktop:
Tweego Version: 2.1.1+81d1d71
OS & Version: linux/amd64
Additional context
This is probably not a severe problem. I don't even know if this should be handled while decompiling or while compiling. My way to work around the problem is to add a space character before ::-webkit-…, so that it is not taken as a new passage.
The - being illegal as the first character of a passage name, the compilation generates an error, which is good.
The easiest solution to handle the problem is maybe to describe it, with a workaround, somewhere in the documentation.
The text was updated successfully, but these errors were encountered:
Describe the bug
When decompiling a file (using
-d
option) and it contains pseudo elements in CSS like ::-webkit-scrollbar, the resulting file cannot be recompiled as the pseudo element is taken as the name of a passage, if the pseudo-element is at the beginning of a line.Expected behavior
I would expect that decompiling and then recompiling any file without modifying it should work.
Desktop:
Additional context
This is probably not a severe problem. I don't even know if this should be handled while decompiling or while compiling. My way to work around the problem is to add a space character before
::-webkit-…
, so that it is not taken as a new passage.The
-
being illegal as the first character of a passage name, the compilation generates an error, which is good.The easiest solution to handle the problem is maybe to describe it, with a workaround, somewhere in the documentation.
The text was updated successfully, but these errors were encountered: