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

 @westonruter I'm polishing some other stuff off and waiting to hear back
 internally as to our ideal path forward.  I'm going to be largely
 deferring to @samhotchkiss and @beaulebens on direction, but I'm happy to
 do what I can to get implementation dealt with once the direction is
 decided.

 One change I would very much like to see in core though is the capability
 being changed from `unfiltered_css` to `edit_css` or the like -- because
 if the cap is going to be remapped, then the name is really bad.  The name
 should be what the capability allows, with the `unfiltered_css` being
 what's tested on saving.  If that makes sense?

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