From 0b7457325200162961cae52e7d871db928dc3cd9 Mon Sep 17 00:00:00 2001 From: Zhe Sun <31067185+ZheSun88@users.noreply.github.com> Date: Thu, 23 May 2019 09:43:31 +0300 Subject: Update broken docs syntax in github (#11596) * Add delay to the unstable test * Add delay for unstable tests * Update broken docs syntax in github * Merge branch 'master' into ZheSun88-patch-1 * Update doc reference syntax * Merge branch 'ZheSun88-patch-1' of github.com:vaadin/framework into ZheSun88-patch-1 # Conflicts: # documentation/components/components-overview.asciidoc * Merge branch 'master' into ZheSun88-patch-1 * use .asciidoc * Merge remote-tracking branch 'origin/ZheSun88-patch-1' into ZheSun88-patch-1 * use .asciidoc * Merge branch 'master' into ZheSun88-patch-1 --- documentation/components/components-progressbar.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'documentation/components/components-progressbar.asciidoc') diff --git a/documentation/components/components-progressbar.asciidoc b/documentation/components/components-progressbar.asciidoc index 54940799b3..f0d5051778 100644 --- a/documentation/components/components-progressbar.asciidoc +++ b/documentation/components/components-progressbar.asciidoc @@ -26,11 +26,11 @@ When the position of a progress bar is done in a background thread, the change is not shown in the browser immediately. You need to use either polling or server push to update the browser. You can enable polling with [methodname]#setPollInterval()# in the current UI instance. See -<> +<<../advanced/advanced-push#advanced.push,"Server Push">> for instructions about using server push. Whichever method you use to update the UI, it is important to lock the user session by modifying the progress bar value inside [methodname]#access()# call, as described in -<>. +<<../advanced/advanced-push#advanced.push.running,"Accessing UI from Another Thread">>. [source, java] ---- @@ -70,7 +70,7 @@ including the progress bar, can be updated either with polling or by using server push. When doing so, you must ensure thread-safety, most easily by updating the UI inside a [methodname]#UI.access()# call in a [interfacename]#Runnable#, as described in -<>. -- cgit v1.2.3