Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)

> @bzbarsky @annevk @domenic @travisleithead : What do you all think about this?

This is a really interesting issue. I guess my initial thought is that we kind of want to run custom element reactions "as often as possible", right? So maybe it is OK to start running them when we prepare a script. I am a little uneasy though as I wish we had a guiding principle that supported such a change, instead of just "let's sprinkle run-CE-reactions as needed".

I wonder if there are other cases where this kind of thing would come up? At first I thought innerHTML might be one, but no, scripts don't execute as a result of fragment parsing.

> If we're trying to solve this problem in more broader sense, and invoke enqueued callbacks before executing any script, then that's a lot more profound change.

I think I agree, but I want to be sure. After all, it would be a very simple and nice principle to say "whenever we run script, we must have already run CE reactions and emptied the CE reactions stack"

Can you think of any other scenarios today where we start running script, and in which the CE reactions stack could be nonempty?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/606#issuecomment-260064154