Changes between Version 3 and Version 4 of Ticket #35395, comment 40
- Timestamp:
- 09/25/2016 10:46:38 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35395, comment 40
v3 v4 19 19 20 20 Even if this finds its way in core, I don't think it needs a preview. As far as I see there are two general user cases: 21 -The users try to change/override some CSS in the theme to perhaps change some colors or hide a component.22 - The users receive a CSS snipped specific to their theme (by the theme author or from support) and want to add it to the site.21 1. The users try to change/override some CSS in the theme to perhaps change some colors or hide a component. 22 2. The users receive a CSS snipped specific to their theme (by the theme author or from support) and want to add it to the site. See [#comment:39 comment 39 above]. 23 23 24 24 In the first case the users will actually need to edit the CSS. However doing that without seeing/knowing the current CSS structure and selectors is pretty much impossible. Anybody that is even a little familiar with CSS would know to open the browser tools and try the changes there. The browser tools are also a lot more comfortable when "hacking" any CSS. You can see all styles and selectors, there is autocomplete, error highlighting, instant preview, etc. We will never be able to match that, and don't really need to. There is no point in adding CSS Editor to WordPress.