Dear Support-Team,
since the new Version of Plain Classes, all classes added via the plugin are also added to the Oxygen Selectors. In the previous Version, this behavior was different.
Especially in combination with Winden, this leads to undesirable results:
- empty classes in Oxygen CSS files (e.g. using TW utility classes)
- performance issues in Oxygen due to many Selectors
- additional Bugs, e.g. when using the Oxygen Button element, its default settings are sometimes applied to the class. When using utility classes, this produces unexpected bugs and makes the Button element unusable
- higher error potential, due to possible unintentional customizations of utlity classes via Oxygen
I am looking forward to your reply!
Kind Regards
Uploaded files:
Hello there,
What issue are you having with empty classes? This was the compromise so we do not need to patch oxygen anymore.
We will improve soon !important of tailwind so it will overwrite oxygen default styles.
Hope that answer your questions or at least partially.
Hello Marko,
thank you for your reply!
This is unfortunate news for me, as this leads to bloated and poor code quality in the long run. Imagine having 200 utility classes in an a project: Why should they be added a second time as an empty definition anywhere in the code? And why are they available in the Oxygen Selector editor, if none of them should ever be customized? And if you have previously used TW classes but removed them from the project, you would have to go through all Oxygen Selectors to find the ones that aren’t used any more, becoming a very ineffective human JIT compiler.
This might be a little pedantic, but it is important to me that the tools I use produce clean results and reduce my workload.
As an idea: Since you have already integrated an auto-complete feature for TW classes, would it be possible to extend this to e.g. auto-lock known TW utility classes, that no one can “accidentally” add styles via the Oxygen selector system?
Unfortunately, this would not fix the bloat-factor, but maybe you can add an option (backend action “Deduplicate CSS”) that walks the Oxygen selectors, compares them with the TW classes & config and removes all duplications…
I hope my ideas may help the plugin’s improvement!
Kind Regards
PS: The additional bug is unrelated and occurs only with Collaboration 2.0.0beta – I will open a separate ticket for this
You are correct for the long run, we will see if we can implement a better solution or improve the current so that the utility classes won’t go in Oxygen selectors, that way, if we stop the sync as previous version, then the lock tailwind classes won’t be required as well.
We will inform more about this if we find a solution in facebook group. I’m closing this ticket now.
Regards,
Mohammad Arshad
DPlugins Support
Thanks, Mohammad, looking forward to an Update on this!
As additional info: As a workaround for the bloat-factor I have now tested “Oxy Cleaner” by OxyPlugins which seems to be doing the job. It scans for unused classes and removes them from the Oxygen selector system – so far without issues.