Opened 9 years ago
Closed 3 months ago
#36527 closed enhancement (wontfix)
Add a 'wp-' prefix to ALL admin classes to prevent CSS conflicts
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | |
Focuses: | ui | Cc: |
Description
Long story short, in any front end editors, which WP itself seems to be moving towards with the Customizer, there are lots of admin elements that are not prefixed and can quickly begin to conflict. Some examples are .button, .textarea, etc. I'd love to see all admin classes add a prefix of .wp-
Change History (4)
#3
@
9 years ago
- Component changed from Customize to Administration
- Focuses accessibility administration removed
- Milestone changed from Awaiting Review to Future Release
- Version trunk deleted
Definitely something I'd love to see too, but there are also big, big, backwards compatibility concerns. For sure, for the sanity of the project, something should be done sooner or later :) See for example this make core post:
https://make.wordpress.org/core/2014/12/19/core-css-roadmap/
"Decide on CSS naming conventions"
Setting the component to administration since "Customize" is specific for the Customizer. Also, the version should be set to the version the bug/feature was first introduced which in this case is... I don't know :) Lastly, removing the accessibility focus since it's not strictly related to accessibility.
#4
@
3 months ago
- Resolution set to wontfix
- Status changed from new to closed
I discovered this one scrubbing tickets missing a milestone.
Unfortunately, I think that this is one thing that we're just stuck with until the administration area of WordPress is redone. There is no way to accomplish this with full knowledge of everything that could break, so the risks outweigh the benefits here.
But, there is work and discussion happening around a new admin experience. The kickoff post is a great place to start.
Thanks for this suggestion, @mrpritchett! It was a good one, just not something that is realistic without breaking backwards compatibility. I'm going to close it out as wontfix
, but it can always be reopened in the future if conditions change. Discussion is also free to continue on closed tickets.
I agree that it would be nice for something to be done here.
While any kind of front-end editing experience has to wrestle with the challenges of trying not to take on theme styles, a good first step would be getting the WordPress editor to style properly across the board on the front-end.
I'd be happy to submit a patch if prefixing the classes is an acceptable solution.