Bug 35246 - mouseout and mouseover events with relatedTarget == null should be sent when exiting/entering the browser
Summary: mouseout and mouseover events with relatedTarget == null should be sent when ...
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-22 10:08 PST by Grant Gayed
Modified: 2017-03-11 10:53 PST (History)
2 users (show)

See Also:

Attachments
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 Grant Gayed 2010-02-22 10:08:29 PST 
- observed with WebKitGTK 1.1.21

- view the page at the bottom with GtkLauncher
- move the mouse into and out of the browser control
  -> the first time the mouse enters a mouseover is received with relatedTarget == null, which is correct
  -> however from this point onwards there are no more mouseover and mouseout events received with relatedTarget == null when moving the mouse into and out of the browser control

<html>
<head>
<script language="JavaScript">
function mousehandler(e) {
  alert(e.type);
  alert(e.relatedTarget);
}
function init() {
  document.onmouseover = mousehandler;
  document.onmouseout = mousehandler;
}
</script>
</head>
<body onLoad="init()">
<textarea rows="2" cols="20">
</textarea>
</body>
</html>