Re: [csswg-drafts] "Single content, multiple renderings" feature for `<selectlist>` (#9284)

IMO this gets pretty complex very quickly. The *closest* thing we have in engines today is repeated headers/footers for tables when printing - but this has lots of complexities - and has the same DOM content. E.g. some implementations just repeat the painting commands at a different offset - e.g. they don't support arbitrary different content. `element()` was mentioned in the IRC log - but this is basically repeating paint commands, not generating two different renderings for the same DOM.

Lots of (complex!) questions would need to be answered (as @smaug---- notes), e.g. what happens during hit-testing, selection() type APIs (which operate off the DOM) etc.

TL;DR avoid if possible.

-- 
GitHub Notification of comment by bfgeek
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9284#issuecomment-1743842972 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 2 October 2023 22:12:36 UTC