I can appreciate the development philosophy, but I don't see a compelling need for a "fix" here. Said fix, as far as I can conceive it, would involve blocking plugin authors from using a (relatively obscure) workaround and prevent — what exactly? Hypothetical style-hijacking? It's not like there are roaming bands of irresponsible plugin authors wrecking people's StyleSheets. Even if there were, people would simply pass on their plugins — or request a fix — or fix them themselves.
Not to sound flip. I think the concerns are real (and good ones). I just don't want to endorse a fix that takes a tool out of the toolbox to combat a problem that's only hypothetical. (If there are real-world examples of the load order causing problems, they're pretty rarified and likely easily addressed.) Speaking of rarified, there's a way I benefit from the refreshStyles type of plugin: I have several TiddlyWikis whose CSS is identical but have different background images. In order to make some elements more readable, I've concoted quick-and-dirty plugins to override the default StyleSheet in those TWs. Install the plugin, turn it on, and the styles adjust for that particular TW without affecting the StyleSheet I use (and update regularly) as my go-to. So it's definitely true that I'm biased in favor of the workaround remaining. ;) -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
