From f6284f7681518838a7076bed3b1049f1c05e0528 Mon Sep 17 00:00:00 2001 From: Jonni Nakari Date: Mon, 15 Feb 2016 15:15:32 +0200 Subject: 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 --- documentation/advanced/advanced-embedding.asciidoc | 20 -------------------- 1 file changed, 20 deletions(-) (limited to 'documentation/advanced/advanced-embedding.asciidoc') diff --git a/documentation/advanced/advanced-embedding.asciidoc b/documentation/advanced/advanced-embedding.asciidoc index ca2ccd3a0e..8c16f99aac 100644 --- 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]#++
++# 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] ----- - ----- - endif::web[] ifdef::web[] @@ -255,13 +242,6 @@ element. - - - -

Embedding a Vaadin UI

This is a static web page that contains an embedded Vaadin -- cgit v1.2.3