[wp-trac] [WordPress Trac] #38672: Custom CSS should work with existing Jetpack custom CSS

[WordPress Trac]

#38672: Custom CSS should work with existing Jetpack custom CSS
-----------------------------+------------------
 Reporter:  helen            |       Owner:
     Type:  defect (bug)     |      Status:  new
 Priority:  highest omg bbq  |   Milestone:  4.7
Component:  Customize        |     Version:
 Severity:  blocker          |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------

Comment (by jorbin):

 Replying to [comment:19 westonruter]:
 > @jorbin I was chatting with @georgestephanis and I think his intention
 is that a single `edit_css` meta capability could be passed as the
 `capability` when the `WP_Customize_Custom_CSS_Setting` is registered.
 With vanilla core this would map to `unfiltered_html` (or
 `unfiltered_css`?) and would thus be restricted to admins/superadmins. A
 plugin (read: Jetpack) which adds a sanitization library could then re-map
 `edit_css` to something more permissive like `edit_theme_options` so that
 users who formerly were unable to edit the CSS could then do so. I don't
 know if it makes sense to have two separate CSS-related meta capabilities.


 I'm cool with that.  My main goal is to ensure 1) vanilla core restricts
 access to the equivalent of `unfiltered_html` ( either in and of itself or
 as `unfiltered_css` ) and 2) At some point in the future, the feature
 doesn't need to be restricted as there is well-tested sanitization
 available in core.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38672#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform