Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668)

Actually, with native CE v1 in Chrome, `innerHTML` is treated atomically, so that `childNodes` is not `0` and `innerHTML` is not empty by the time life cycle methods are called! Basically CE behaviors are not triggered until the DOM created from innerHTML is ready. This is inconsistent with initial DOM parsing.

-- 
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/668#issuecomment-334988964