Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321389 - [BrowserFunction] returns immediatly when showing a dialog
Summary: [BrowserFunction] returns immediatly when showing a dialog
Status: CLOSED WONTFIX
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.3   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-30 13:28 EDT by Philipp Leusmann CLA
Modified: 2014-04-08 05:22 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Leusmann CLA 2010-07-30 13:28:25 EDT 
Build Identifier: 

When opening a Dialog from a BrowserFunction, the Javascript side does not wait for the dialog to close, but instead goes on immediatly.
This means, it is not possible for a BrowserFunction to request user input using a dialog and return the result.

As a workaround we currently use the HtmlResponseWriter to "inject" the result into the browser, which of couse leads to serious timing problems.

Reproducible: Always
Comment 1 Ivan Furnadjiev CLA 2010-08-09 04:44:53 EDT 
I can confirm that it works in SWT, but not in RAP.
Comment 2 Ivan Furnadjiev CLA 2010-12-09 03:56:46 EST 
This issue is complicated, because on the client (javascript) we have single-thread model - both browser function and UI work in the same thread. If we block the BrowserFunction on the client to wait for the result, the dialog (GUI) become unresponsive and the application is locked. The "injection" of the result is the only feasible solution.
Comment 3 Tim Buschtoens CLA 2014-04-08 05:22:52 EDT 
It's not a critical issue, there seems to be no feasable fix, and there has been no activity for years. Closing this as wontfix.