Namespace class names about prism HOT 4 CLOSED

They are, in the CSS. They are used with .token, like .token.comment. I find it highly unlikely that .token.whatever will clash with author styles.

from prism.

That doesn't help because you can still end up with specificity problems. All it takes if for someone (e.g. a wordpress user) to have CSS like #comments .comment and then any code in a comment is going to be affected. Hence, either namespace the classes or use !important in the theme CSS.

from prism.

can't they get around that by tag qualifying the other code? Prism’s .comments are spans, I doubt WP .comments are.
I really like the sensible class names it currently has (they're one of the 6 advantages listed in the header), so I'm very reluctant to throw this away for the possibility of a collision. After all, if an author wants to customize the token names, it's trivial.

from prism.

I don't think you need to throw them away, but it's also sensible to protect your plugin from author styles without relying on them making other changes to their code. Hope you'll consider adding a simple namespace or the option to do so. Thanks

from prism.