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

@bahrus I'm not sure how you would suggest that we replace processing instructions in the current proposal with `<template>` and what benefit `<template>` has to mark nodes and child node ranges rather than processing instructions/comments? Ack that we could throw data into a `<template>` in attributes or other child nodes, but I don't think that's much easier than just parsing metadata as JSON or whatever in userland.

The question is whether or not comments should mark the beginning and end of a child node range. Meaning, if you remove one of the comment nodes from the DOM, the range would be invalid, and whatever nodes are between the two comments be precisely what the range represents, rather than some abstract non-DOM based concept of a child node range where you would have to explicitly add or replace nodes in the range via a new API, and sibling additions would have no impact (which leads to unintuitive behavior like if a node gets added in between two nodes that are part of the range, should that node be part of the range too?). It's really a question of whether the placeholders representing ranges should be serialized to the DOM as nodes (in the declarative case, comment nodes, but in the imperative case whatever nodes the user provides) or not.

Not sure I understand what a "flat" element possibility would be, perhaps you could explain.

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

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