On Thursday, August 26, 2021 at 4:47:09 AM UTC+2 [email protected] wrote: ...
> The plugin (at v1.0.0) used only text I specified as innerHTML to append > my stylesheet before tw's so to avoid unnecessary !important's and > specificity in the CSS, > I did see the !important declaration already. You and the users won't be happy with it, since the theme CSS will be really hard to tweak by users. There will be cases, where we see !important !important ... Which is possible but similar to "a shoot in the foot". If you search Google for "CSS important harmful" you will find some articles. One of the more resent ones: https://uxengineer.com/css-specificity-avoid-important-css/ !important has a reason why it exists. It can be used if there is absolutely no other way. ... but ... If you need it for almost every element in your CSS there is a major flaw in the whole system. IMO it will be better to rethink this. I don't have a solution, since I didn't have a closer look. ... but I can say one thing. Plopping an alien CSS toolkit onto TW will most of the time create more problems as it solves. You did dig already into the TW UI and the CSS structure. IMO it would save you a lot of trouble and time, if you would try to understand it and use the possibilities that TW gives you, instead to try other "shiny" toolkits, that have been designed with a completely different philosophy and usecase behind it. just my thoughts. -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a2e04e2c-70fe-4bd8-9314-0c2c05a27e68n%40googlegroups.com.
