- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 15 Nov 2024 06:21:10 -0800
- To: w3c/selection-api <selection-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 15 November 2024 14:21:14 UTC
I don't understand how this is an implementation detail. Typically we don't have to define implementation details. This we have to define however as it's very much observable. I'm also not sure how the composed range can be computed on the fly. I also don't really understand the slides unfortunately. They suggest that `getRange(0)` allocates, but I think the range stays 1:1 with the selection for the lifetime of the selection. And changes to the range are reflected in the selection and vice-versa. You could do some lazy initialization perhaps, but that would in fact be an implementation detail and would not need to be specified. Similarly the steps under what `setBaseAndExtent()` would do are confusing. First it updates this's composed range and then it replaces it? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/selection-api/issues/2#issuecomment-2479002884 You are receiving this because you are subscribed to this thread. Message ID: <w3c/selection-api/issues/2/2479002884@github.com>
Received on Friday, 15 November 2024 14:21:14 UTC