Webcomponents randomly not rendered

[AndyOGo]

Somehow importing our custom Web Components into Chrome by HTML Imports randomly triggers a weird bug in Chrome, which results in rendering the component in one place but not in another.

Switching to pure ESnext based import's seems to make Firefox some troubles #25 :

TypeError: window.customElements is undefined

This bug isn't reasonable and needs to be 1000% fixed.

Todo

• Make 1000% sure to understand the cause of this bug - no guessing. Ideally easily observable by failing test.
• order of components lifecycle has to be deterministic
• Report this bug to Chrome's issue tracker and link it's issue here
• find reliable cross-browser, testable workaround / bugfix
• document above solution, and communicate it to everyone involved
• make sure that every single web component can be reliable rendered in all supported browsers

[LucaMele]

Recommendation is to use only Custom Element from the Web-Components and not HTML Imports, therefore this issue can be a nice to have

[AndyOGo]

I agree with avoiding HTML imports.

[AndyOGo]

It seems that lifecycle execution (constructor, connectedCallback, attributeChangedCallback, disconnectedCallback, etc.) of hierarchical/nested components is NOT deterministic.
I face this weird behaivior at #34 regarding contextual scope #31

Example:

<axa-parent>
  <axa-child></axa-child>
</axa-parent>

Expected:

`axa-parent` constructor
`axa-child` constructor
`axa-child` connectedCallback
`axa-parent` connectedCallback

Observed (parent after child):

`axa-child` constructor
`axa-child` connectedCallback
`axa-parent` constructor
`axa-parent` connectedCallback

[LucaMele]

Exactly, like proposed specs describe it.

[LucaMele]

As HTML imports are not reccomended, we keep this issue as very low prio

[LucaMele]

i think is fixed.. feel free to reopen in case is not

[AndyOGo]

I don't know if it's fixed 🤔
Though I haven't seen it a while and we aren't using HTML imports.