Re: [w3c/webcomponents] [IDEA] deferred upgrade. (#559)

Does the issue make sense? Let me know if I need to explain it differently. Essentially, I never have any problem if my elements *don't have to be upgraded* (i.e. the classes are registered before the elements are ever created). The problems arrise when the elements are created before the classes are registered, in which case they need to be upgraded, and in which case *causes some of my library code to execute before all the classes have been registered and therefore the code can fail because the custom element classes are minimally coupled*.

-- 
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/559#issuecomment-243246330