Re: [w3c/webcomponents] document.close doesn't need CEReactions (#597)

OK.  So as I said, I _think_ that can't happen based on briefly skimming the parser state machine, but....

Whats the downside of triggering cereactions on close()?  Just extra code?  Seems like it should be a no-op if we're lucky, so the only reason to not be doing it is optimization or something, right?

-- 
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/597#issuecomment-256750430