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

Bug 385943

Summary: Mouselistener on Browser with Flowdocument content does not work
Product: [Eclipse Project] Platform Reporter: Marcus Öberg <chippen>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact: Grant Gayed <grant_gayed>
Severity: normal    
Priority: P3 Keywords: triaged
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Sample Flowdocument file none

Description Marcus Öberg CLA 2012-07-25 09:52:28 EDT
Build Identifier: M20110909-1335

This is similar to the old bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=49696

It seems that if you add a mouseListener to a swt browser it will be called if the content is normal web content. But in my case the content is a Flowdocument file with .xaml extention. I guess that the flowdocument steals the mouse clicks so that it isn't visible to my listener.

This is my first bug report so please tell me if i did something wrong or if i need to explain better (Or if this i not acually a bug but is the expected behaviour).



Reproducible: Always

Steps to Reproduce:
1. Create new shell
2. Add Browser
3. setUrl to file://filelocation 
4. register mouseListener with new MouseAdapter on browser


I include a small example of a Flowdocument to put in the *.xaml file:

<FlowDocumentReader xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation">
<FlowDocument>
<Paragraph>Foo bar</Paragraph>
</FlowDocument>
</FlowDocumentReader>
Comment 1 Marcus Öberg CLA 2012-07-25 09:54:49 EDT
Created attachment 219156 [details]
Sample Flowdocument file
Comment 2 Marcus Öberg CLA 2012-07-26 04:11:02 EDT
This seems to apply to the KeyListeners too.
Comment 3 Grant Gayed CLA 2012-07-30 12:37:25 EDT
These listeners are not currently expected to work in non-HTML pages because the events are hooked in the DOM.  That being said, it's not unreasonable to expect a case like this to work.  Moving report to triaged.
Comment 4 Leo Ufimtsev CLA 2017-08-03 12:27:20 EDT
This is a one-off bulk update. (The last one in the triage migration).

Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process:
https://wiki.eclipse.org/SWT/Devel/Triage

See Bug 518478 for details.

Tag for notification/mail filters:
@TriageBulkUpdate
Comment 5 Eclipse Genie CLA 2020-02-03 17:12:07 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.