Re: [w3c/webcomponents] How to wait for will-be custom elements to be upgraded? (#558) from Joe Pea on 2018-01-28 (public-webapps-github@w3.org from January 2018)

From: Joe Pea <notifications@github.com>
Date: Sun, 28 Jan 2018 03:08:16 +0000 (UTC)
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/558/361034595@github.com>

@domenic @kojiishi `whenDefined()` only works when the library author knows the names that library constructors will be assigned to.

This is currently difficult to work with without using [ugly deferral hacks and leaking memory](https://github.com/w3c/webcomponents/issues/674).

@rniwa's [`whenUpgraded(elementInstance)` idea](https://github.com/w3c/webcomponents/issues/671#issuecomment-333006549) would help here, but it can still leak memory if the element names associated with constructors are not known.

-- 
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/558#issuecomment-361034595

Received on Sunday, 28 January 2018 03:08:43 UTC