[wp-trac] [WordPress Trac] #31436: Handle conflicts in concurrent Customizer sessions

[WordPress Trac]

#31436: Handle conflicts in concurrent Customizer sessions
-------------------------+-----------------------------
 Reporter:  westonruter  |       Owner:  westonruter
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  Future Release
Component:  Customize    |     Version:  3.4
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:  javascript
-------------------------+-----------------------------

Comment (by celloexpressions):

 Replying to [comment:13 azaozz]:
 > Locking the customizer when in use is a really good idea. Locking
 individual settings in the customizer seems too much. The customizer, and
 the rest of the settings screens are not used frequently. Also settings
 usually require an admin level user to change, so collisions are likely to
 occur only on sites with many admins (which are quite rare).
 >
 > In that terms a general per-user lock for any settings screen, including
 the customizer, seems best.
 In terms of thinking towards the future, and particularly potential future
 uses of the Customizer API potentially including content, having per-
 setting locking would be awesome.

 This is certainly a forward-looking proposal and may take a few releases
 to get right, but if we can go all the way and do it per-setting we'll set
 ourselves up really nicely for future additions and use-cases.

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