Re: Default empty custom.css
Reply #1 –
Provided the topic would fit better the features discussion board (from my understanding), my thought is: in an ideal world, the default theme shall not have it, because it would be the equivalent of having a file named Settings.php in the home: at the next update (or file overwrite for any reason) it would be wiped out along with all the custom code.
For themes created by the admin panel it would be very nice to have I guess.
Actually, this makes me think the "correct" behaviour of the editing page should be to always work only on copies of the defaul theme, and if none exists, then silently create one. That would make it easier to deal with the customizations I think. It would likely require one more step on saving (i.e. ask the admin if he wants to apply the changes to all the users), but would be cleaner.