Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340266 - The IE9 document model does not support MouseEnter and MouseExit event.
Summary: The IE9 document model does not support MouseEnter and MouseExit event.
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-16 23:43 EDT by zhaojian CLA
Modified: 2019-11-08 04:40 EST (History)
1 user (show)

See Also:

Attachments
plugin project (4.55 KB, application/octet-stream)
2011-03-16 23:45 EDT, zhaojian CLA 		no flags Details
plugin project (5.30 KB, application/octet-stream)
2011-03-17 00:30 EDT, zhaojian 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 zhaojian CLA 2011-03-16 23:43:28 EDT 
Build Identifier: M20080911-1700

If the content property value of meta element in the html file is defined as IE=9, when the html file is being loaded through the SWT.Brower class, the audio monitor of MouseEnter and MouseExit event cannot be triggered.


Reproducible: Always

Steps to Reproduce:
For details, please run the attached plugin project.
Comment 1 zhaojian CLA 2011-03-16 23:45:01 EDT 
Created attachment 191373 [details]
plugin project
Comment 2 Nitin Dahyabhai CLA 2011-03-16 23:51:49 EDT 
I think you'll need to reattach that using a more common archive format, like zip or jar, and perhaps try a 2011 build instead of one from 2008.
Comment 3 zhaojian CLA 2011-03-17 00:30:10 EDT 
Created attachment 191374 [details]
plugin project

For details, please run the attached plugin project.
Comment 4 Lars Vogel CLA 2019-11-08 04:40:47 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.

If you have further information on the current state of the bug, please add it. 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.

If the bug is still relevant please remove the stalebug whiteboard tag.