Make WordPress Core

Opened 14 months ago

Last modified 2 months ago

#39099 new defect (bug)

Customize: Defer triggering selective refresh for all settings until after synced

Reported by: westonruter Owned by:
Milestone: 5.0 Priority: normal
Severity: normal Version: 4.7
Component: Customize Keywords: has-patch needs-testing
Focuses: Cc:


Selective refresh is triggered when a setting is added, changed, or removed. In the case of being added, there are scenarios where infinite full refresh can ensue if a partial has fallback refresh. This has been particularly evident for nav menus. While the infinite refreshes have largely been fixed for nav menus in #38612, there are still cases more generally where settings could be registered in the controls (admin) but not in the preview (pane). In the case of nav menus, this still causes a selective refresh to happen even at an initial page load.

This is essentially revisiting #37032.

Attachments (2)

39099.0.diff (1.7 KB) - added by westonruter 14 months ago.
39099.1.diff (2.1 KB) - added by westonruter 7 months ago.

Download all attachments as: .zip

Change History (15)

#1 @westonruter
14 months ago

  • Keywords has-patch added

Something that I still want to address is the scenario where a user may make a change to a postMessage-transport setting while a full refresh is happening. In that case, we *do* want there to be an initial selective refresh happening.

#2 @westonruter
14 months ago

Easiest way to reproduce this issue is to activate the Nav Menu Roles plugin and prevent a few menu items from being displayed when a user is logged in. When loading the customizer preview, the menu containing these excluded items will get initially selective-refreshed.

#3 @westonruter
14 months ago

  • Milestone changed from 4.7.1 to 4.8

#4 @celloexpressions
12 months ago

  • Version set to 4.7

+1, if we can eliminate the initial selective refresh for menus, even, this would be a big improvement. If the changes aren't too much more complex after addressing 1, I think it's worth getting this into the 4.7 branch.

#5 @westonruter
12 months ago

  • Keywords needs-testing added

This ticket was mentioned in Slack in #core by flixos90. View the logs.

8 months ago

#7 @flixos90
8 months ago

  • Milestone changed from 4.8 to Future Release

7 months ago

#8 @westonruter
7 months ago

  • Milestone changed from Future Release to 4.9

#9 @westonruter
7 months ago

I noticed infinite refresh happening in Twenty Fifteen in 4.8 when deleting a menu assigned to a nav menu location.

This ticket was mentioned in Slack in #core by melchoyce. View the logs.

3 months ago

#11 @westonruter
3 months ago

  • Milestone changed from 4.9 to 4.9.1

I've not been noticing this and I haven't heard it reported. Punting.

This ticket was mentioned in Slack in #core by westonruter. View the logs.

3 months ago

#13 @johnbillion
2 months ago

  • Milestone changed from 4.9.1 to 5.0
Note: See TracTickets for help on using tickets.