- From: Mason Freed <notifications@github.com>
- Date: Mon, 18 Sep 2023 09:32:43 -0700
- To: w3c/selection-api <selection-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 18 September 2023 16:32:49 UTC
Similar to [my reply on #79](https://github.com/WICG/webcomponents/issues/79#issuecomment-983868870), I agree. Your summary above sounds exactly right to me. The devil is in the details, but the broad strokes look correct. > What might be tricky is that if someone accesses getRange(0) and manipulates that, this selection live range needs to be updated as well (or perhaps thrown away). We need to be careful not to introduce loops there. Seems like that operation (manipulation of a live range) should go through the same "update selection" algorithm which should take care of the details. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/selection-api/issues/168#issuecomment-1723905897 You are receiving this because you are subscribed to this thread. Message ID: <w3c/selection-api/issues/168/1723905897@github.com>
Received on Monday, 18 September 2023 16:32:49 UTC