Thanks for your detailed reply @eladalon1983. The article you linked to answers several questions; thanks for that too. It would be really helpful for review, and future reference, if you could that content from the article into the explainer; it's OK to give a bit of the 'how to' info, as long as the explainer starts with the user needs being solved. That info, and the code snippets, helps to convey the intended API shape. There are a couple of additional things that we'd really like to see in the explainer: * Please could you include some info on whether elements that are outside of the viewport (i.e. elements that are not visible) would be capture-able? (Your info on `display: none` is noted.) * We asked about Viewport Capture, and in your reply, you address this as one alternative that was considered. Please could you include an 'Alternatives considered' section in the explainer, and mention the rationale re Viewport Capture - and any other approaches that you considered? Thanks in advance; we are looking forward to learning more about the above. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/954#issuecomment-2344584220 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/954/2344584220@github.com>
Received on Wednesday, 11 September 2024 19:54:53 UTC