[wp-trac] [WordPress Trac] #36485: Lost pending customizer settings after theme change

[WordPress Trac]

#36485: Lost pending customizer settings after theme change
-------------------------------------+--------------------------
 Reporter:  mikeschroder             |       Owner:  westonruter
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  4.7
Component:  Customize                |     Version:  4.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  javascript
-------------------------------------+--------------------------
Changes (by westonruter):

 * keywords:  needs-patch => has-patch needs-testing


Comment:

 This has been implemented in the patch for #30937.

 Please test: `grunt patch:https://github.com/xwp/wordpress-
 develop/pull/161`

 As noted there: now when you make a change to a `theme_mod` in theme A
 (like change background color to red) and then switch to another theme B
 and activate it instead, the next time you open theme A in the customizer
 for live preview the changes you made previously will be applied as your
 customizer state (the color will be background color will be red again).
 This is implementing [https://wordpress.slack.com/archives/core-
 customize/p1475701646001630 feedback] from @jorbin:

 > With this feature I would strongly encourage thinking in terms of user
 flow.
 >
 > For example, "As a user, when I am live previewing and making changes to
 the twentyseventeen theme and then switch to live previewing the twentyten
 theme, I expect the customizations I made to twentyseventeen to be there
 the next time I live preview it"

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