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
I've a very strange issue.
I can debug the css before it gets written in the file and it includes the sourcemap, but in the css-file this sourcemap is not written.
I verified the 2 compiler classes and the hook and didn't find any fault.
It looks like the file is written in another location or at another time without the sourcemap, as it's just included in the content-string. So actually I don't have a clue why the sourcemap is missing in the css and how this issue could be fixed.
ws_scss: 11.0.3
TYPO3: 11.5.21
PHP: 8.1.24
Apart from very few additions I just use EXT:demotemplate, to give an idea about the parsed files.
The text was updated successfully, but these errors were encountered:
this screenshot doesn't tell anything special more, but it shows some details to support my statements (the line number doesn't synchronize to the public version):
tail in the debug is defined like this:
'tail' => substr($result->getCss(), -200, 200)
and the debug is positioned above these three lines:
Finally I got a glimpse what's happening, there are indeed 2 different css files written, even I don't understand the reason.
Links in the page look always like this:
I've a very strange issue.
I can debug the css before it gets written in the file and it includes the sourcemap, but in the css-file this sourcemap is not written.
I verified the 2 compiler classes and the hook and didn't find any fault.
It looks like the file is written in another location or at another time without the sourcemap, as it's just included in the content-string. So actually I don't have a clue why the sourcemap is missing in the css and how this issue could be fixed.
ws_scss: 11.0.3
TYPO3: 11.5.21
PHP: 8.1.24
Apart from very few additions I just use EXT:demotemplate, to give an idea about the parsed files.
The text was updated successfully, but these errors were encountered: