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

Are there any notes of what was discussed that led to doubts whether {{}} is a feasible authoring tool?  If it isn't a feasible authoring tool, then there doesn't seem much point to supporting interpolation beyond what spans can provide.  However, I think the **output** of what is rendered needs to provide enough information so we can reverse engineer everything.

I earlier endorsed (to the wind, I'm sure) the comment idea, but if my quick analysis is correct that the cost of a processing instruction matches the cost of an empty template, templates would be much easier to apply an xslt transform to reverse engineer the server rendered content to extract the data and {{}} based template (which would keep the syntax the originating template needs to support simpler).

A quick lookup indicates comments can be used for ranges, so not sure where that question came from either.  Maybe there's some more subtle nuance I'm missing?

I also did my usual second guessing about  the possibility of using "flat" elements (no bookending) to model nested structures.  I don't yet have 100% in *my* solution.  But I remember now where I got the idea.  There are actually plenty of robust grids (starting with slickgrid) that managed this quite well (using "levels" to keep track of the nested structure).  This would reduce the number of (unnecessary) elements, I think, which could only help performance.  At least something to consider?



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

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