Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990)

If we want to support the server-side rendered HTML use case, we'll need some way of annotating HTML without a `<template>`. So, in some ways, if we want to have a single syntax for defining DOM parts in HTML, we'll need to start with that more basic use case, rather than the `<template>` instantiation use case.

The DOM parts API is solving use cases outside template instantiation - I think the server-side hydration use case (locate some nodes in a big chunk of HTML if you know ahead of time which nodes you'll need) is really exciting, and can't be solved easily if we only have a `<template>` based syntax.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/990#issuecomment-1478661517
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/990/1478661517@github.com>