| 12 | | The logic for adding the `customize_autosaved` param to the frontend preview URL (#39896) should get improved, in case a plugin does want to preview the autosaved state. In the mean time, the preview link feature is only intended for previewing the fully saved state, not autosaves. |
| | 12 | The logic for adding the `customize_autosaved` param to the frontend preview URL (#39896) should get improved, in case a plugin does want to preview the autosaved state. In the mean time, the preview link feature is only intended for previewing the fully saved state, not autosaves. Nevertheless, the `customize_autosaved=on` preview URL may not ultimately have the changeset autosave revision fully populated yet since pending changes are sent in POST requests before being written into the changeset at the autosave interval. |
| | 13 | |
| | 14 | Having the `customize_autosaved=on` param present currently leads to unexpected results whereby a previewer sees changes that the author doesn't intend to share yet. |