Title: Plugin generic classes clash with Tailwind 4
Last modified: May 20, 2026

---

# Plugin generic classes clash with Tailwind 4

 *  [wigglypoppins](https://wordpress.org/support/users/wigglypoppins/)
 * (@wigglypoppins)
 * [2 weeks, 5 days ago](https://wordpress.org/support/topic/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](https://wordpress.org/support/users/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 2 weeks, 5 days ago by [wigglypoppins](https://wordpress.org/support/users/wigglypoppins/).

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-generic-classes-clash-with-tailwind-4%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/coblocks/assets/icon-256x256.jpg?rev=2243972)
 * [Page Builder Gutenberg Blocks – CoBlocks](https://wordpress.org/plugins/coblocks/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/coblocks/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/coblocks/)
 * [Active Topics](https://wordpress.org/support/plugin/coblocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/coblocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/coblocks/reviews/)

## Tags

 * [class](https://wordpress.org/support/topic-tag/class/)
 * [conflicts](https://wordpress.org/support/topic-tag/conflicts/)
 * [styles](https://wordpress.org/support/topic-tag/styles/)
 * [Stylesheet](https://wordpress.org/support/topic-tag/stylesheet/)

 * 0 replies
 * 1 participant
 * Last reply from: [wigglypoppins](https://wordpress.org/support/users/wigglypoppins/)
 * Last activity: [2 weeks, 5 days ago](https://wordpress.org/support/topic/plugin-generic-classes-clash-with-tailwind-4/)
 * Status: not resolved