[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:16 westonruter]:
 > Re: [attachment:38672.diff] should `edit_css` map to `unfiltered_html`
 according to the same rules as how `unfiltered_html` maps? In other words,
 should `DISALLOW_UNFILTERED_HTML` still be considered or whether it is
 multisite and the user is a superadmin? It seems the mapping could also be
 done as:
 >
 > Or should it map to `unfiltered_css`, a brand new primitive capability?
 Or should we re-use the `unfiltered_html` primitive?

 What about having two capabilities:  `unfiltered_css` and `edit_css`.
 right now, both would map to `unfiltered_html`.  Plugins could remap them
 as they see fit (such as if they implement a sanitizer, mapping `edit_css`
 to `customize` ).   In the future, core could decide that `edit_css`
 should be mapped to something else.

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