"platform-view-1"

<div

id=

"platform-view"

>Contents

</div>

</flt-platform-view>
  ...

</flt-glass-pane>

...

After this change, when the framework needs to move DOM nodes around, it
operates over flt-platform-view-slots, which only contain a slot element.
The slot projects the contents defined in flt-platform-view elements outside
the shadow root. flt-platform-view elements are never the target of DOM
operations from the framework, thus preventing the reload issues.

From an app’s perspective, this change is transparent. However, this is
considered a breaking change because some tests make assumptions
about the internal DOM of a Flutter web app, and break.

Migration guide

Code