Augustine Kim

https://github.com/lit/lit/blob/2407c808007268c1f96f14e311eb36d525080968/packages/lit-html/src/lit-html.ts#L888-L906 Looks like we already warn for `` and throw for `` but don't account for things like `` since we'd normally not expect to see a `` tag in...

There might be some overlap but I think it's valid to keep this a separate issue from #1983 which asks for Service Worker rendering (in the browser) versus handling non-browser...

This has been superseded by the conversion to hybrid decorators

I've seen the "extra attributes from the server" errors while trying out solutions for https://github.com/lit/lit/issues/3418 as well. This might be unavoidable so it's worth considering suppressing this via https://react.dev/reference/react-dom/client/hydrateRoot#suppressing-unavoidable-hydration-mismatch-errors which...

Per offline convo with @justinfagnani this is something we could have bespoke handling in the `@lit-labs/react` wrapper where we're able to check property options and include it to the host...

The hydration warnings are specifically happening when the server add attributes that weren't included in the original template as props. Having defaults on the server won't prevent that. To prevent...

So the logic would be to patch `createElement` (and runtime JSX functions) so that if the tag provided is a Lit component, look at the Lit component class, find all...

We've done a team huddle on this and we're going with adding `suppressHydrationWarning` client-side for these components. @aneta-kjeldsen your concern about the pitfall > This approach makes hydration slower because...

Discussed this case a bit more during our eng meeting just now. Since the `suppressHydrationWarning` prop needs to be set on the client side, we can easily do this for...

I think it would be good to add an option to the plugin that will add suppressHydrationWarning prop to Lit components client side. The option could even take an array...