Open wkbkhard opened 11 months ago
It seems that if you change back to the barceloneta theme (over design configuration) the development-css of that theme will be used
I played around a bit and checked the different files - something I stumbled upon is the "sources" and "sourceRoot" in the css Files. Maybe those can't be read by the development tools or something like that... still shouldn't be a thing if you use official tools. Will investigate some more and update here if I find something
Okay - it seems there are 2 problems. First one is the ignorance of the "development-css" in the manifest as I described above and therefore still a CMFPlone Problem I guess.
The other one is that the compilation of the CSS files and maps seems to be off. After some research and a lot of help I added a postcss.config.js with the following code in my theme:
module.exports = { map: false, }
Now the Source Maps seem to be okay when I have the manifest.cfg updated to:
production-css = ++theme++my-theme/styles/theme.css
I don't now where to put an Issue for the second problem. Any suggestions?
BUG/PROBLEM REPORT
Developing CSS for own barceloneta-based theme seems to not fully work as expected - in development-mode (registry) and with a development-client it won't show the split up CSS files in development tools in browsers etc.
What I did:
What I expect to happen:
What actually happened:
What version of Plone/ Addons I am using: