newpage undo problem

[Garry Yao]

Reproducing Procedures

1. Open the replace by class example page in FF;
2. Click 'New Page' to empty document;
3. Press 'Undo' button;
   • Expected Result: The original document has been reverted.
   • Actual Result: The document remains empty, and actually you need two more 'Undo' to revert it back.

[Garry Yao]

The problem with 'New Page' command is it's sort of asynchronized command that we can 't fire 'afterCommandExec' immediately, if that, the snapshot is been taken even when document content is not loaded.

[Garry Yao]

The patch is about supporting asynchronous command, say, now first on 'New Page'.

[Alfonso Martínez de Lizarrondo]

I didn't look at this part still, but this is one part that I think it would be better if it can be changed from V2 (people has lots of problems with it)

The question is: does the SetHTML really needs to be asynchronous? Can't we work directly with the existing document when the user wants to change it instead of being forced to create a new one?

If the answer is maybe, then I think that this patch shouldn't be applied (at least for the moment), and a new ticket to change SetHTML (or its current equivalent) to make it synchronous should be open.

What do you think?

[Garry Yao]

yes, alfonsoml, this should be put discusssion, but it's not a little change, and I guess the major problem without reload the iframe is about the stylesheet, when 'New Page' is asked, ideally we should has a clean document or I am wrong?

[Artur Formella]

Currently this code doesn't work after istanceReady event:

editor.setData("aa");
b= editor.getData();

It would be great to work with the existing document, but it would be too big change for beta version. I thing we should open a new ticket for discussion.

[Garry Yao]

I'm closing this one and opening #3732 for discuss alfonsoml's proposal.
Fixed with [3668].