Skip to content

fix: Update use of HydrationElementController to only be used during initial load #7170

@janechu

Description

@janechu

🐛 Bug Report

Currently defer-and-hydrate does not get applied in the forCustomElement method of the HydratableElementController. This should be rectified and assumed that defineAsync() is being used as this option currently only works in a flakey manner when using define().

Additionally the following logic should be added:

  • 'hydrate' should apply the needs-hydration attribute only
  • These attributes should only be applied if hasExistingShadowRoot is true during component instantiation, this ideally should be bypassed in future by another system that determines if the page is being evaluated during a first load and then defer back to the ElementController instead of the HydratableElementController

Metadata

Metadata

Labels

Type

No type

Projects

Status

Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions