[wp-trac] [WordPress Trac] #38549: Additional CSS lost when changing themes

[WordPress Trac]

#38549: Additional CSS lost when changing themes
--------------------------+-----------------------------
 Reporter:  scottwyden    |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Customize     |     Version:  4.7
 Severity:  normal        |  Resolution:
 Keywords:  needs-design  |     Focuses:
--------------------------+-----------------------------
Changes (by dlh):

 * keywords:   => needs-design
 * milestone:  Awaiting Review => Future Release


Comment:

 There are a lot of user-friendly ideas here, but it seems to me like it
 now need someone to hash out a prototype, either in a rough patch or as a
 mockup, to begin the process of iteration.

 Replying to [comment:3 westonruter]:

 > Instead of there being an option to push the CSS into another theme when
 switching, it would probably be preferred to have a dropdown to pull CSS
 from another theme. So if you're editing a twentyseventeen child theme you
 there could be a dropdown for importing CSS from twentyseventeen parent
 theme.
 >
 > Aside: the CSS pulled from the other theme would need to first check the
 current changeset to see if there are any CSS changes for that theme
 stored in it, and if so, use those instead of the changes in the
 `custom_css` post type for that theme.

 Perhaps there's a dropdown that allows the user to first view the custom
 CSS saved in another theme in a read-only field, which might be enough for
 the use case of plucking a few styles to reuse in the new theme (akin to
 comment:8). Then, if the current changeset also is free of CSS changes, a
 button could also be available to copy the whole thing into the new theme.

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