- From: Mason Freed <notifications@github.com>
- Date: Fri, 17 Jun 2022 10:58:08 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 17 June 2022 17:58:20 UTC
FYI, the TAG just [concluded their design review](https://github.com/w3ctag/design-reviews/issues/694#issuecomment-1147664032) of the new design, and they said they were reasonably happy with the shape. They did raise one question: > One thing we wondered about: once this is implemented are there any remaining use cases for getRangeAt()? It seems that the new method covers all of them, and since it returns a static range it's more performant and less error-prone. If that assumption is correct, would it make sense to deprecate getRangeAt() and name the new method in a more generic way (e.g. getRange())? It seems like a reasonable question. I believe `getComposedRange()` should be usable for all use cases, including any covered by `getRangeAt()`. Perhaps we should rename and deprecate as they recommend? -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/79#issuecomment-1159112560 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/79/1159112560@github.com>
Received on Friday, 17 June 2022 17:58:20 UTC