Slot Changes Re-Rendered in Wrong Location on IE11/Edge

[umdjm]

Stencil version:

 @stencil/core@1.7.5

I'm submitting a:
[ X] bug report
[ ] feature request
[ ] support request

Current behavior:
Adding child element to a slot on IE11 or Edge displays below template.

Expected behavior:
Element displays adjacent to original slot content.

Steps to reproduce:
Open https://umdjm.github.io/StencilFallbackDemo/ on IE11
Code https://github.com/umdjm/StencilFallbackDemo

Related code:

  render() {
    return <div>
      HEADER
      <br/>
      SLOT GOES HERE (
        <slot />
      )
      <br/>
      FOOTER
    </div>;
  }

    <my-component>
      <p> Initial Slot Data </p>
    </my-component>

Other information:

IE Screenshot

Chrome Screenshot

[umdjm]

When I change vdom-render to not reset checkSlotRelocate, I can get this to work on IE with a MutationObserver in my component.

export class MyComponent {
  observer!: MutationObserver;
  connectedCallback() {
    this.observer = new MutationObserver(this.handleChildrenChange);
    this.observer.observe(this.host, { childList: true });
  }

  @Element() host: HTMLElement;
  handleChildrenChange = () => {
    (this.host as any).forceUpdate();
  };

This does not seem like the right fix, but maybe this can help point others to a better fix?

[dutscher]

it seems tobe related to #1968
cheers

[umdjm]

Nice - thanks @dutscher. Did you also see #1197 which had a commit yesterday: 5ea2a48

[dutscher]

@umdjm i updated the repo to 1.8.0 and the rerender bug still exists.
see here https://dutscher.github.io/stencilslots/

cheers

[umdjm]

This is fixed for me in v1.8.0 (thanks to #1197).

I still have to add a MutationObvserver as mentioned in #2004 (comment).

I'm having other issues with React using IE11 Stencil Components, but I'll try to create a tight repro and open that separately.

[umdjm]

FYI - @dutscher is still having issues with parent and child re-renders but my simpler use case looks fixed.

[umdjm]

Opened #2012 to track the React issue mentioned in #2004 (comment)