Bug 102666 - [Shadow DOM]: Retargeting of relatedTarget algorithm doesn't work
Summary: [Shadow DOM]: Retargeting of relatedTarget algorithm doesn't work
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 102681
Blocks: 103230
  Show dependency tree / graph
 
Reported: 2012-11-19 02:08 PST by Sergey G. Grekhov
Modified: 2012-12-06 03:01 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 Sergey G. Grekhov 2012-11-19 02:08:29 PST 
Please run the following example in Chrome (my Chrome 23.0.1271.64 m):

<html>
<head>
<script type="text/javascript">
function test() {
    var d = document;
    var SR = window.ShadowRoot || window.WebKitShadowRoot;

    //Shadow root to play with
    var s = new SR(d.querySelector('#host'));

    var div1 = d.createElement('div');
    div1.setAttribute('style', 'height:100%; width:100%');
    div1.setAttribute('id', 'div1');
    s.appendChild(div1);
    
    var div2 = d.createElement('div');
    div2.setAttribute('style', 'height:100%; width:100%');
    div2.setAttribute('id', 'div2');
    d.body.appendChild(div2);
    
    d.body.addEventListener('mouseover', function(event) {
    	alert('event.relatedTarget.id=' + event.relatedTarget.getAttribute('id'));
    }, false);
    
    
    var evt = document.createEvent("MouseEvents");
    evt.initMouseEvent("mouseover", true, false, window,
      0, 10, 10, 10, 10, false, false, false, false, 0, div1);
    
    div2.dispatchEvent(evt);
}
</script>
</head>
<body onload="test()">

<div id="host">
</div>

</body>
</html>


As you can see related target is "div1" but according http://www.w3.org/TR/shadow-dom/#retargeting-related-target expected relatedTarget is "host"
Comment 1 Hayato Ito 2012-12-06 03:01:51 PST 
I've confirmed that http://trac.webkit.org/changeset/136818 fixed this. Closing.