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 20982 - [Shadow]: Event retargeting algorithm optimization/clarification
Summary: [Shadow]: Event retargeting algorithm optimization/clarification
Status: RESOLVED LATER
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18428
  Show dependency tree / graph
 
Reported: 2013-02-12 17:47 UTC by Dimitri Glazkov
Modified: 2013-05-09 21:29 UTC (History)
1 user (show)

See Also:

Attachments

Description Dimitri Glazkov 2013-02-12 17:47:57 UTC 
From annevk:

http://lists.w3.org/Archives/Public/public-webapps/2013JanMar/0374.html

--
I was wondering if this rewrite of 3.1-3.3 is correct:

1. Let CONTEXT be null.
2. If ANCESTOR is an insertion point, set CONTEXT to the top-most item
in STACK that is not an insertion point, if any.
3. If STACK is empty, push ANCESTOR on STACK.

I think this would be quite a bit clearer.
Comment 1 Dimitri Glazkov 2013-05-09 21:29:52 UTC 
(In reply to comment #0)
> From annevk:
> 
> http://lists.w3.org/Archives/Public/public-webapps/2013JanMar/0374.html
> 
> --
> I was wondering if this rewrite of 3.1-3.3 is correct:
> 
> 1. Let CONTEXT be null.
> 2. If ANCESTOR is an insertion point, set CONTEXT to the top-most item
> in STACK that is not an insertion point, if any.
> 3. If STACK is empty, push ANCESTOR on STACK.
> 
> I think this would be quite a bit clearer.

The new algo is not going to work quite the same way, since we need to always push an item on stack when ANCESTOR is an insertion point.

Let me close this for now, I need to rework that whole algo anyway.