summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEnver Haase <enver-haase@users.noreply.github.com>2016-04-08 11:59:13 +0200
committerMarko Grönroos <magi@vaadin.com>2016-05-02 12:55:16 +0000
commit355914195bb9167374b252929c138fcabdbec509 (patch)
tree97b0bd76cd86ba0ac30906970b2721ebd2b84e98
parent39b2142869f8b890eb451ae68ba0ad19bbb0ff63 (diff)
downloadvaadin-framework-355914195bb9167374b252929c138fcabdbec509.tar.gz
vaadin-framework-355914195bb9167374b252929c138fcabdbec509.zip
Update clientside-debugging.asciidoc
Change-Id: I2c5c962bdd572b697b992046a139d8d8f653133f
-rw-r--r--documentation/clientside/clientside-debugging.asciidoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/clientside/clientside-debugging.asciidoc b/documentation/clientside/clientside-debugging.asciidoc
index efbe24a8ec..13a3249ea6 100644
--- a/documentation/clientside/clientside-debugging.asciidoc
+++ b/documentation/clientside/clientside-debugging.asciidoc
@@ -116,7 +116,7 @@ Chrome supports source maps, which allow debugging Java source code from which
the JavaScript was compiled.
Open the Chrome Inspector by right-clicking and selecting [guilabel]#Inspect
-Element#. Click the settings icon in the lower corner of the window and check
+Element#. Click the settings icon in the upper right corner of the window and check
the "Scripts > Enable source maps" option. Refresh the page with the Inspector
open, and you will see Java code instead of JavaScript in the scripts tab.