- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Feb 2014 11:53:28 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24010 Hayato Ito <hayato@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Hayato Ito <hayato@chromium.org> --- (In reply to Erik Arvidsson from comment #0) > 6.3 Event Retargeting, retargeting algorithm > > "4. Let RELATIVE-TARGET-TREE be the lowest common inclusive ancestor tree of > CURRENT-TARGET-TREE and ORIGINAL-TARGET-TREE > " > > Thes two nodes might not have a common ancestor. I assume the algo should > hst return null in that case As long as the current target and the relative target are in the same tree of trees, there must be the lowest common inclusive ancestor tree. The current spec doesn't mention anything about what should happen if the current target and the related target are in different tree of trees. However, that should not happen in the context of event dispatching, I think. Let me close this bug. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 6 February 2014 11:53:29 UTC