Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334138 - [Browser] Refactor BrowserFunction creation
Summary: [Browser] Refactor BrowserFunction creation
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.4 M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 330806
  Show dependency tree
 
Reported: 2011-01-12 12:10 EST by Tim Buschtoens CLA
Modified: 2011-01-19 06:17 EST (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 Tim Buschtoens CLA 2011-01-12 12:10:07 EST 
BrowserFunctions are currently sent to the client immediately, where the Browser.js tries to add them to the document every 100ms. Besides the risk of forever having a useless function be called every 100ms, it prevents propper processing of cross-domain errors. 

The solution would be for the server to wait until the document is loaded, indicated by the progress event.
Comment 1 Tim Buschtoens CLA 2011-01-18 08:25:07 EST 
We had a discussion and came to an alternative solution: The browserFunction will be created on the onload event, but directly on the client, not by the server-response. Therefore a list of all browserFunctions needs to be maintained on the client.
Comment 2 Tim Buschtoens CLA 2011-01-19 06:17:20 EST 
Fixed in CVS HEAD.