aboutsummaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorIlia Motornyi <elmot@vaadin.com>2018-04-20 13:43:21 +0300
committerGitHub <noreply@github.com>2018-04-20 13:43:21 +0300
commitab547965fd91038618d0199055fd229035ed5da9 (patch)
treea974f408c56b21f913ec3eb81ee6256c968e72f8 /documentation
parent0b2b05138ec2bced6d73cecf3d78b0c934cfa91e (diff)
downloadvaadin-framework-ab547965fd91038618d0199055fd229035ed5da9.tar.gz
vaadin-framework-ab547965fd91038618d0199055fd229035ed5da9.zip
Add MenuItem notices to BrowserWindowOpener documentation (#10820)
Diffstat (limited to 'documentation')
-rw-r--r--documentation/advanced/advanced-printing.asciidoc4
-rw-r--r--documentation/advanced/advanced-windows.asciidoc2
-rw-r--r--documentation/articles/OpeningAUIInAPopupWindow.asciidoc2
3 files changed, 4 insertions, 4 deletions
diff --git a/documentation/advanced/advanced-printing.asciidoc b/documentation/advanced/advanced-printing.asciidoc
index 0443f43cbe..22f0ed2ca2 100644
--- a/documentation/advanced/advanced-printing.asciidoc
+++ b/documentation/advanced/advanced-printing.asciidoc
@@ -107,12 +107,12 @@ To print content as PDF, you need to provide the downloadable content as a
static or a dynamic resource, such as a [classname]#StreamResource#.
You can let the user open the resource using a [classname]#Link# component, or
-some other component with a [classname]#PopupWindowOpener# extension. When such
+some other component with a [classname]#BrowserWindowOpener# extension. When such
a link or opener is clicked, the browser opens the PDF in the browser, in an
external viewer (such as Adobe Reader), or lets the user save the document.
It is crucial to notice that clicking a [classname]#Link# or a
-[classname]#PopupWindowOpener# is a client-side operation. If you get the
+[classname]#BrowserWindowOpener# is a client-side operation. If you get the
content of the dynamic PDF from the same UI state, you can not have the link or
opener enabled, as then clicking it would not get the current UI content.
Instead, you have to create the resource object before the link or opener are
diff --git a/documentation/advanced/advanced-windows.asciidoc b/documentation/advanced/advanced-windows.asciidoc
index 0e8b5351a6..60245dc910 100644
--- a/documentation/advanced/advanced-windows.asciidoc
+++ b/documentation/advanced/advanced-windows.asciidoc
@@ -93,7 +93,7 @@ public static class MyPopupUI extends UI {
=== Popping It Up
A popup window is opened using the [classname]#BrowserWindowOpener# extension,
-which you can attach to any component. The constructor of the extension takes
+which you can attach to any component or `MenuItem`. The constructor of the extension takes
the class object of the UI class to be opened as a parameter.
You can configure the features of the popup window with
diff --git a/documentation/articles/OpeningAUIInAPopupWindow.asciidoc b/documentation/articles/OpeningAUIInAPopupWindow.asciidoc
index d9f3208244..a9afde00ea 100644
--- a/documentation/articles/OpeningAUIInAPopupWindow.asciidoc
+++ b/documentation/articles/OpeningAUIInAPopupWindow.asciidoc
@@ -10,7 +10,7 @@ Opening a UI in a popup window
To open a new popup window in the browser showing another part of your
application, you can use the new `BrowserWindowOpener` extension. Any
-component that you extend with `BrowserWindowOpener` will make clicking
+component or `MenuItem` that you extend with `BrowserWindowOpener` will make clicking
the component open a new browser window with some options for the
content. Opening a popup this way helps you bypass most popup blockers.