Plugin generic classes clash with Tailwind 4

I’ve noticed that one of your css files (coblocks/dist/style-coblocks-1.css) has included a bunch of generic Tailwind type classes (e.g. p-1, p-2, mr-1, etc.) with different style values to the default Tailwind styles for these classes.

This wasn’t an issue until updating to Tailwind v4 which now outputs utilities inside @layer utilities {}, while your unlayered CSS will always beat layered CSS regardless of document order so changing load order doesn’t do a thing

I feel that including any generic classes in a plugin is bound to cause issues and conflicts for people using it, especially when it’s contained in a stylesheet with other quite specific classes meaning it can’t just be dequeued without breaking how the elements from your plugin look.

I suggest you either put these classes inside its own stylesheet in your plugin so that it can be dequeued, replace these generic class names with something more specific to your plugin (e.g. cb-p-1, cb-p-2, cb-mr-1, etc.) or just include these styles in the specific classes that need them.

I wouldn’t have spotted it or even mind that much if the class styles matched up with Tailwind’s values but the fact that they’re using em values rather than rem is a bit daft and including them in the first place seems quite short sighted for the people using your plugin.

Edit: upon further inspection, it doesn’t seem like you’re even using these classes anywhere within the plugin which is even more criminal

• This topic was modified 3 days, 3 hours ago by wigglypoppins.