Adrian Cochrane on Nostr: Code reuse would be vital, so I'd introduce glob-matching of properties & types. And ...
Code reuse would be vital, so I'd introduce glob-matching of properties & types.
And we'd need a "collection" type which we can concatenate, map (possibly referencing previous item), filter/query (possibly referencing candidate response), & sort. Primarily this would be used for process a node's children (incurring postorder traversals), as well as at-rules & maybe parsed url()-referenced resources.
Also include pseudo-elements & literal text, so they can be spliced into the children.
2/3?
And we'd need a "collection" type which we can concatenate, map (possibly referencing previous item), filter/query (possibly referencing candidate response), & sort. Primarily this would be used for process a node's children (incurring postorder traversals), as well as at-rules & maybe parsed url()-referenced resources.
Also include pseudo-elements & literal text, so they can be spliced into the children.
2/3?