[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):

 @lukecavanagh I know. But if we replace `unfiltered_css` with `edit_css`
 as the meta capability, should we introduce a new `unfiltered_css`
 primitive capability to map it to by default, or should we map it to the
 existing `unfiltered_html`? And if so, should we follow the same
 conditionals for honoring `DISALLOW_UNFILTERED_HTML` and multisite?

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