This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24010 - [Shadow]: What if there is no common ancestor?
Summary: [Shadow]: What if there is no common ancestor?
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Hayato Ito
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14978
  Show dependency tree / graph
 
Reported: 2013-12-05 20:47 UTC by Erik Arvidsson
Modified: 2014-02-06 11:53 UTC (History)
1 user (show)

See Also:

Attachments

Description Erik Arvidsson 2013-12-05 20:47:16 UTC 
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
Comment 1 Hayato Ito 2014-02-06 11:53:28 UTC 
(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.