[Bug 22459] [Custom]: Consider explicitly emptying callback queue in more cases

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

--- Comment #22 from Dominic Cooney <dominicc@chromium.org> ---
(In reply to comment #21)
> It's illogical to receive a 'left' signal before 'entered', that's true.
> 
> I admit to not being aware of all the ins and outs of this algorithm. I
> probably should have kept my mouth shut. 

I value your feedback. Maybe the best thing is to try last week's proposal with
actual components? It should be in tomorrow's Chrome Canary.

> I only meant to say we didn't need special processing in the specific case
> you originally described, in the hopes this made things easier on you.

This specific case is probably a corner case. It is the kind of thing where the
implementation must do something but it is easy to do either one. It is
literally moving one line of code to three lines earlier in a couple of places.

For now I've implemented the one where a Custom Element's callback queue is
only scheduled earlier if there *is* a callback to run.

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

Received on Tuesday, 9 July 2013 02:43:10 UTC