Context Navigation

Changes between Initial Version and Version 1 of Ticket #39275

Ticket #39275
- Property Summary changed from Improve wp.customize.previwer.save() for changesets. to Improve wp.customize.previewer.save() for changesets.

initial	v1
1		If you do not pass any status in `wp.customize.previwer.save()` the changeset status becomes published because the default `changesetStatus` is `publish` in core, which compels you to pass a status if you want to save the changeset with any other statuses like `draft/pending/future` however that eventually creates a revision. So if you do not want to create revisions there is no option except hacking the `customize_save` ajax request probably with `$.ajaxPrefilter`.
	1	If you do not pass any status in `wp.customize.previewer.save()` the changeset status becomes published because the default `changesetStatus` is `publish` in core, which compels you to pass a status if you want to save the changeset with any other statuses like `draft/pending/future` however that eventually creates a revision. So if you do not want to create revisions there is no option except hacking the `customize_save` ajax request probably with `$.ajaxPrefilter`.
2	2
3		So I think if we do not pass any status in `wp.customize.previwer.save()` it should just save the changeset to the previous status set.
	3	So I think if we do not pass any status in `wp.customize.previewer.save()` it should just save the changeset to the previous status set.
4	4	Also it would be nice if it had a param like `skip_revision` which skips creating new revision.