Re: [WICG/webcomponents] Spring 2023 DOM Parts F2F (Issue #999)

One (perhaps the only?) viable alternative if we must support the table element as is, would be empty template elements, which was the direction [I was going](https://github.com/bahrus/be-repeated#example-v----compatibility-with-server-rendered-lists) before I learned of the ability to query processing instructions with xpath.  I was able to get nested loops working without bookending before and after, relying instead on the cnt attribute.  But I only tested that two levels deep, and didn't yet convince myself it wouldn't run into trouble as the complexity of scenarios increased.  So I would be hesitant to adopt that solution without far bigger implementations from high usage libraries trying it out.

As my comments indicate, I would have preferred using the data element, as that seems to be its purpose, but as I recall, table elements spit them out as well.

Has anyone done performance comparisons between the two? (empty template elements vs processing instructions).  Yes, my intuition tells me processing instructions would win out, but you never know, I guess?

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

Message ID: <WICG/webcomponents/issues/999/1513817935@github.com>