GWT history frame is not needed in embedding

Vaadin is not anymore using the type of GWT History support that would need the __gwt_historyFrame iframe.

Change-Id: Ibd5414ddd744b3a570bb7b23700a616ca7ee56bf

diff --git a/documentation/advanced/advanced-embedding.asciidoc b/documentation/advanced/advanced-embedding.asciidoc
index ca2ccd3a0eb3dc96f61150153e7a297c9271f8af..8c16f99aac702522c184423a1b30bcf417f7f7c1 100644 (file)
--- a/documentation/advanced/advanced-embedding.asciidoc
+++ b/documentation/advanced/advanced-embedding.asciidoc
@@ -34,7 +34,6 @@ different widget sets and different themes.
 Embedding an UI requires the following basic tasks:
 
 * Set up the page header
-* Include a GWT history frame in the page
 * Call the [filename]#vaadinBootstrap.js# file
 * Define the [literal]#++<div>++# element for the UI
 * Configure and initialize the UI
@@ -95,18 +94,6 @@ relative to the path of the embedding page.
 The bootstrap script is served by the Vaadin servlet from inside the
 [filename]#vaadin-server# JAR.
 
-Vaadin, or more precisely GWT, requires an invisible history frame, which is
-used for tracking the page or fragment history in the browser.
-
-
-[source, html]
-----
-  <iframe tabindex="-1" id="__gwt_historyFrame"
-          style="position: absolute; width: 0; height: 0;
-                 border: 0; overflow: hidden"
-          src="javascript:false"></iframe>
-----
-
 endif::web[]
 
 ifdef::web[]
@@ -255,13 +242,6 @@ element.
   <script type="text/javascript"
           src="VAADIN/vaadinBootstrap.js"></script>
 
-  <!-- GWT requires an invisible history frame. It is   -->
-  <!-- needed for page/fragment history in the browser. -->
-  <iframe tabindex="-1" id="__gwt_historyFrame"
-          style="position: absolute; width: 0; height: 0;
-                 border: 0; overflow: hidden"
-          src="javascript:false"></iframe>  
-
   <h1>Embedding a Vaadin UI</h1>
     
   <p>This is a static web page that contains an embedded Vaadin