This issue is related to  issue 1293  (
http://code.google.com/p/google-web-toolkit/issues/detail?id=1293 )

In  issue 1293  I do the add and remove by creating a new instance of RichTextArea. I
am forced to use a field to save the html before removing the RichTextArea and to set
the html from that field once the new instance is loaded and the waiting timer has
been called. The reason I took this approach is because as mentioned above, a not
initiliazed exception is thrown when calling UIObject.setVisible(boolean visible) on
the Panel that contains the RichTextArea thus removing and adding doens't quite work.
Maybe the same goes for setVisible?

Any unit test written for this should be able to pass after multiple adds/remove of
the widget. setVisible should probably be also be tested. There is a catch where the
html is properly set and can be get from a visible RichTextArea BUT the RichTextArea
does NOT display the html (Behaviour documented in  Issue 1293 ).

(No comment was entered for this change.)

(No comment was entered for this change.)

RichTextAreaImplStandard does not, in fact, recreate the iframe each time it's
initialized. What's happening is that every browser except for IE wipes the dynamic
contents of an iframe when it's removed from the DOM and re-added. We're going to
have to maintain the contents manually and put them back upon re-initialization.

I added code in RichTextAreaImplStandard.java to preserve the iframe's contents when
an RTA is removed & re-added. There is also a test now to ensure this doesn't get
broken in the future.

(No comment was entered for this change.)

Fix committed as r1305.

1.4 RC2 now released.