[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:  high          |   Milestone:  4.7
Component:  Customize     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------

Comment (by beaulebens):

 Replying to [comment:2 lukecavanagh]:

 I'm not really sure what you're saying. Are you saying we should just
 leave things as they are, and ship both? That seems really confusing, not
 to mention redundant for users.

 We can definitely look at making changes to how the Jetpack one works, if
 it makes sense to bring it into line with something core is shipping, or
 even look at just porting differences over to what core ships, and
 deprecating ours entirely.

 At the moment, it looks like the proposed core one only exists in the
 Customizer, and is theme-specific. It's a basic textarea only.

 Jetpack's, on the other hand, is _not_ in the Customizer (appears as
 Appearance > Edit CSS), and is "global" (not theme-specific). It is a
 syntax-highlighted textarea, saves revisions, and also allows for pre-
 processing if the user desires.

 We could look at merging this functionality, or we (Jetpack) can perhaps
 just make it so that our editor comes in as an upgrade to what core
 provides.

 At the very least, it seems like it would make sense to make the way
 things are stored be compatible?

 Can you (or someone) point me to any decision process around why the core
 editor is theme-specific vs global perhaps? That seems like one of the
 most fundamental actual differences right now.

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