- From: <bugzilla@jessica.w3.org>
- Date: Mon, 14 May 2012 04:10:52 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16176 Hayato Ito <hayato@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #19 from Hayato Ito <hayato@chromium.org> 2012-05-14 04:10:51 UTC --- Thank you for updating the spec, Dimitri! (In reply to comment #18) > http://dvcs.w3.org/hg/webcomponents/rev/80a9f05d1661 <-- stick a fork in it! > > Folks, please look over and reopen bug if I'd done bad. I've taken a look it. Let me reopen this issue since there are some points to be fixed. About 6.2 Retargeting relatedTarget; > 2. Let ANCESTOR be ADJUSTED That should be '2. Let ANCESTOR be RELATED'. > 1. If there is a DOM node that is a member of CANDIDATES and is in the same subtree as TARGET, let ADJUSTED be this DOM node There may be multiple candidates in the same subree. In such case, we should pick up "the lowest'"candidate from the candidates. > 2. Otherwise, let TARGET be the result of running the parent calculation algorithm with TARGET as input That should not be 'the parent calculation algorithm'. The next TARGET should be either 'TARGET.parentNode() or TARGET.host(). If we use 'parent calculation algorithm' here, ADJUSTED might be a node which is not accessible from the NODE. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 14 May 2012 04:10:58 UTC