[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 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.

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