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

>I'm not particularly fond of borrowing from XML in syntax that looks like a blend between PHP (<?=...?>) and custom elements (<my-tag>). Could this not be done without introducing a new node type to HTML that resembles custom elements?

I agree 100%.  In a previous comment, a supporter of this proposal raised an objection to a counter suggestion I made, because my  suggestion didn't make semantic sense.  I agree, and have effectively withdrawn my counter proposal for that reason.  But is was kind of the pot calling the kettle black.  This is precisely why using processing instructions seems like a bad idea -- it is clearly distorting the semantic purpose of what processing instructions are for, where the "target" is supposed to represent a target **application** that the processing instruction is for.  It makes sense for php, because php is an application.

If there is a performance benefit to identifying server makers identifying parts, before downloading the template which would also indicate where the parts are, there are so many existing semantically meaningful markers we could choose from, including [microdata](https://github.com/WICG/webcomponents/issues/1013) and [aria-](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques attributes, such as aria-rowindex, aria-owns, etc.  If there is a scenario where these fall short, it seems like a wasted opportunity not to work on enhancing these existing vocabularies.

Perhaps a middle ground would be this:  

We support a name for a meta tag that could go in the header of the HTML document, or in an HTTP header, that specifies what markers to look for that indicates parts.  The content could include a list of xpath and/or css matches to search for.

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

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