[Bug 23887] [Shadow] Put only the final destination insertion point to the event path

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887

--- Comment #165 from Olli Pettay <bugs@pettay.fi> ---
(In reply to Koji Ishii from comment #164)
> Hayato and I discussed today and came up with a new proposal, in the hope of
> achieving both-win.
Don't understand what "both-win" refers to.

> 
> The proposal is to add an exception to the spec:
> 
> CURRENT:
> The event path calculation algorithm must be used to determine event path
> and must be equivalent to processing the following steps
> 
> PROPOSED:
> The event path must be equivalent to processing the event path calculation
> algorithm described below, except that insertion points may appear in
> different order, as long as they’re after the content distributed to them
> (or fallback content in the case of fallback) and before their parents
I don't understand what this all means.

> Still we needed to try hard to come up with a better algorithm, one because
> mental models vary by people, and the other because all of us want this
> algorithm simple and fast, while the “simple and fast” was different by the
> underlying architecture.
> 
> The algorithm in the current spec works good for Blink architecture, while,
> as far as I understand from the discussion in Bugzilla, it adds insanely
> complex burden to Gecko.
The main issue with the current algorithm in the spec is its inconsistency and
mentally really
hard to get right. 
What is wrong with the proposed change + the fix similar to comment 163?

I very much thought we had agreement here and just had to tweak the proposed
algorithm a bit.

> On the other hand, we implemented the proposed new algorithm, but we figured
> out that it makes our code more complex, and we are still unable to fix 3
> regressions.
> 
What regressions?



> Our conclusion is to allow implementation dependency in the manner of not to
> trouble web developers is the only way to make all of us happy.
I hope you don't mean we would have implementation specific event dispatch?
That is something Gecko will not do.
Shadow DOM will not be enabled by default before we have a good enough spec for
it and the implementation follows it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 26 February 2015 15:14:38 UTC