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

Bug 342428

Summary:	[Browser] Block browser when not enabled
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 M7
Hardware:	All
OS:	All
Whiteboard:

Description Tim Buschtoens

2011-04-11 08:38:09 EDT

In SWT when the browser widget gets disabled( "setEnabled( false )"), the user can no longer interact with the browser content. We should do the same in RAP. There actually already are "block()" and "release()" implementations in IFrame.js, we just have to use them.

Comment 1 Tim Buschtoens

2011-04-11 08:40:29 EDT

As disabled browser would then probably also support different mouse-cursors.

Comment 2 Tim Buschtoens

2011-04-11 08:42:16 EDT

For some reasion release() is alrady called Browser#_onload. This is probably incorrect.

Comment 3 Ivan Furnadjiev

2011-04-11 09:07:48 EDT

(In reply to comment #2)
> For some reasion release() is alrady called Browser#_onload. This is probably
> incorrect.
If I remember correctly, this release() call is added here to avoid two clicks to activate a link in the browser - first click was needed to remove the blocker.

Comment 4 Ivan Furnadjiev

2011-04-14 03:21:13 EDT

Fixed in CVS HEAD by overwritting the _applyEnabled method to block/release the blocker. I removed the release() in Browser#_onload as it does not make any change.