Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) from Ryosuke Niwa on 2017-10-08 (public-webapps-github@w3.org from October 2017)

From: Ryosuke Niwa <notifications@github.com>
Date: Sun, 08 Oct 2017 09:38:57 +0000 (UTC)
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/668/334994701@github.com>

You really can't rely on your children being upgraded like that. HTML parser can add more children as it parses things, and there's no way to know when that happens. It could be before or after `setTimeout(~, 0)`. FWIW, it could be being blocked by the network!

See https://github.com/w3c/webcomponents/issues/619

-- 
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-334994701

Received on Sunday, 8 October 2017 09:39:19 UTC