Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361271 - [Browser] Doesn't support LocationListener properly
Summary: [Browser] Doesn't support LocationListener properly
Status: RESOLVED WONTFIX
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 11:44 EDT by Sebastian Bauer CLA
Modified: 2011-11-03 02:29 EDT (History)
0 users

See Also:

Attachments
The example mentioned in my report. (1.21 KB, text/x-java)
2011-10-18 11:46 EDT, Sebastian Bauer CLA 		no flags Details
View All 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 Sebastian Bauer CLA 2011-10-18 11:44:27 EDT 
Build Identifier: 

I will attach a small example that uses a browser widget. It adds a LocationListener to this widget which simply logs the events. The browser is supposed to display a simple html text document that contains a link referring to an external location. If I click on the link, none of the methods is called (they are only called once due to the setText()). This is different to SWT where the methods called also when I click them.

Reproducible: Always
Comment 1 Sebastian Bauer CLA 2011-10-18 11:46:06 EDT 
Created attachment 205434 [details]
The example mentioned in my report.
Comment 2 Ivan Furnadjiev CLA 2011-10-21 03:26:47 EDT 
Sebastian, Browser widget is an iframe inside a real browser. Due to browser security policies, it's not possible to find if the URL of the Iframe is changed (by clicking on a link) or not. I think that there is no clean and 100% reliable way to do this in all supported by RAP browsers.
Comment 3 Ralf Sternberg CLA 2011-10-21 05:00:09 EDT 
There is nothing we can do about this issue in the browser client. Therefore I have to close this bug as WONTFIX, sorry.
Comment 4 Sebastian Bauer CLA 2011-10-21 06:03:57 EDT 
You could add a little note somewhere, because this behaviour is definitively different from the SWT library.
Comment 5 Ivan Furnadjiev CLA 2011-11-03 02:29:12 EDT 
(In reply to comment #3)
> There is nothing we can do about this issue in the browser client. Therefore I
> have to close this bug as WONTFIX, sorry.
Closed as WONTFIX.