Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)

@rictic , even if the syntax just a placeholder, the principle of attributes vs dom parts markup by same convention is important to separate on current discussion level. It can be done as in backward compatible as in breaking fashion. The parts within attribute already  have a built-into-browser solution: XSLT convention. The dom parts as well: either as custom element or `<xsl:value-of>`

I see the proposal as attempt to swing away from ability to reuse the existing platform features along with complimentary advantages without matching compensation.

The `<part>` is the good approach which can be generated by whatever syntax the build toolchain support whether it is JSX or mustache syntax. But the reverse ( as in proposal) is not that easy. 

There is a compromise which can/should come with separate proposal: the source DOM alias: 
`✂️=<part>` using either html entities extension of another mechanism. This way the mustache `{{` would be aliased to `<part>` or another string in parsing time. But if we would state the synthetic syntax upfront, that opportunity would not be an option. 

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

Message ID: <WICG/webcomponents/pull/1023/c1661422432@github.com>