- From: flavi1 via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Jan 2019 17:32:28 +0000
- To: public-css-archive@w3.org
Okay!... I think the root problem is older. Honestly i doesn't agree with the confusion between style blocks space and selector definition space introduced by actual preprocessors. I think that increase sementic and structure dependencies between css and html. Then i think preprocessors functions are not bad, but in this context appears like the antidote of its own poison... But it's another discussion. And if people wants it, i will need to deal with :) Never mind. I will keep my started idea as a separate preprocessor css-compatible > So, it's unlikely that @import will be changed in this way. If it ever does, it'll be a separate proposal that relaxes the @import restrictions in general, allowing it to show up between rules as well. If it happens one day, it should be better to call it "@include" to avoid possible confusion and respect retro-compatibility... Then i will add "@include" in my preprocessor. Thanks for this note! -- GitHub Notification of comment by flavi1 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2909#issuecomment-458225832 using your GitHub account
Received on Monday, 28 January 2019 17:32:30 UTC