WordPress.org

Make WordPress Core

Changes between Initial Version and Version 6 of Ticket #30028


Ignore:
Timestamp:
01/23/2015 05:31:47 PM (4 years ago)
Author:
westonruter
Comment:

Moving this to 4.2 since the issue would be resolved by #30937.

The new communications channel mentioned in the description is the “Customize transactions” proposed in #30937. Instead of the current Ajax POST + document.write() approach for populating the Customizer preview, the patch developed for that ticket implements the loading of the preview iframe with a normal GET request for the desired URL with a transaction ID query argument added.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30028

    • Property Milestone changed from Awaiting Review to 4.2
  • Ticket #30028 – Description

    initial v6  
    44
    55Another gotcha here, perhaps another reason why `document.write()` was chosen for populating a blank iframe, is maintaining the scroll position when a refresh happens. Doing a `location.reload()` in the preview window may not have a seamless preservation of the scroll position. We may need to make sure the Customizer preview gets sent back with output buffering so that the entire document is sent all at once so that incremental rendering does not interfere with the prior scroll position.
     6
     7Fixes #23225