Proposal: Inline Components

[loreanvictor]

Inline components are web components that render their content directly on the host element instead of the shadow root. This sacrifices encapsulation in favor of enabling pre-rendering. In the long run, hopefully something in lines of declarative shadow DOM gets standardised and need for inline components would vanish.

Requirements:

• Except for stuff that explicitly rely on encapsulation (e.g. adding stylesheets), the component body should be unaware of the fact that it is an inline component.
• All hooks must work (will they?)
• Minimal code for making this work (ideally just the base component class).

[loreanvictor]

Perhaps this could also be a separate lib? It might be a good idea to keep API surface minimal.

Additionally, relationship between inline components and static components needs to be considered, as static components are only useful for SSR, which currently only makes sense if they are inline. But two questions remain:

• Are inline, non-static components, a useful concept?
• Isn't it enough to simply not include the code for static components in the bundle? In that case, isn't the concept tightly coupled with a particular SSR solution?

[loreanvictor]

seems like Safari added support for DSD and the Mozilla team is also positive, which, alongside Chrome already supporting the feature, might make this proposal obsolete. will keep it open for now, both to track standardisation of DSD, and also to contemplate other potential use cases for inline components.