Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hydrating static content #4297

Closed

Conversation

tanhauhau
Copy link
Member

@tanhauhau tanhauhau commented Jan 21, 2020

assuming server render content is correct, if the content is static, then can skip hydrating it's children.

  • mainly no more deoptimisation for cases where .innerHtml is used.
  • still need to claim the 1st level elements, because they are needed for cleanup when unmounting the component

possibly fixes: #2152

changes built on top of #4444

@tanhauhau tanhauhau changed the title hydrating static content WIP: hydrating static content Jan 21, 2020
@tanhauhau tanhauhau force-pushed the tanhauhau/hydrating-static-content branch from a643c1d to aa077e2 Compare February 21, 2020 01:23
@tanhauhau tanhauhau force-pushed the tanhauhau/hydrating-static-content branch from aa077e2 to 89b7cf6 Compare February 22, 2020 12:06
@tanhauhau tanhauhau force-pushed the tanhauhau/hydrating-static-content branch from 89b7cf6 to 281860e Compare February 22, 2020 12:16
@tanhauhau tanhauhau changed the title WIP: hydrating static content hydrating static content Feb 22, 2020
@Conduitry
Copy link
Member

I'm going to close this, because we need to spend more time thinking about how we want hydration to work, and how we'll tell the compiler where it's safe to do the 'easier' hydration where we assume the starting DOM is correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Request: Some sort of support for .innerHTML optimization with hydratable
2 participants