- From: Di Zhang <notifications@github.com>
- Date: Fri, 07 Mar 2025 15:41:29 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 7 March 2025 23:41:33 UTC
dizhang168 created an issue (whatwg/dom#1363) ### What is the issue with the DOM Standard? Per the [discussion](https://github.com/whatwg/dom/pull/1342#discussion_r1962059510) on the PR to define Composed Selection Range, there is a disagreement on what naming we should use for the new concept. Currently: * Composed selection range: A range with start and end endpoints that can be across shadow trees * Legacy selection range: The live range that is associated with the composed selection range. In Selection API, this is the live range returned by getRangeAt(0). Some suggestions on how to call it includes: 1. "composed live range" and "legacy live range" 2. "composed selection range" and "legacy selection range" 3. "composed-tree selection range" and "same-tree selection range" 4. "composed selection range" and "same-tree selection range" Does anyone have a strong preference? @annevk @smaug---- @sefeng211 @domfarolino -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1363 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1363@github.com>
Received on Friday, 7 March 2025 23:41:33 UTC