Have you checked what you can do with the event SavingContent?

ServiceLocator.Current.GetInstance<IContentEvents>().SavingContent += this.SavingContent;

public static void SavingContent(object sender, ContentEventArgs e)
{
    .. Do your stuff ...
}

I haven't found a backup for this setting. There was a bug a few releases back when it didn't autosave when editing xhtml string, but that should be fixed now.

>There was a bug a few releases back when it didn't autosave when editing xhtml string, but that should be fixed now.

Could you please give a link to the issue number ?

Currently we have issue with publishing xhtml string that was not autosaved: http://world.episerver.com/forum/developer-forum/EPiServer-Commerce/Thread-Container/2016/2/autosave-issue-in-the-tinymce-in-the-blocks/

Ah now I understand your question. A common way to make sure that the property is saved is to click outside the property field. Could that work for you?

We will give the recommendation to the content editors.

Unfortunately, it doesn't help always. Sometimes the autosave does not work if the user clicks outside the xhtml. The case is block with one xhtml string.

Could you please check the http://screencast.com/t/Vr4vx0tENVsK ? The clicking outside doesn't help (block with one wysiwyg).

The browser

@Sviatlana, I think this might be a separate issue than Axandor's, let's continue this in your own thread. http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=144823

Yes, I'll move to it. Thank you for answers.