Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334138

Summary:	[Browser] Refactor BrowserFunction creation
Product:	[RT] RAP	Reporter:	Tim Buschtoens <tbuschto>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	tbuschto
Version:	1.4
Target Milestone:	1.4 M5
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	330806

Description Tim Buschtoens

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

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

2011-01-19 06:17:20 EST

Fixed in CVS HEAD.