Re: [w3c/editing] Track: Selection API for Shadow DOM (Issue #403)

Just to confirm - I do plan to attend this Thursday's meeting, and I've put together a very small handful of slides to review the [Shadow Selection API Proposal](https://github.com/mfreed7/shadow-dom-selection#readme). I will share the slides a bit closer to the date, but is this issue the appropriate place to share them? Or is there an agenda issue or something somewhere?

> > I believe `getComposedRange()` should be usable for all use cases, including any covered by `getRangeAt()`. Perhaps we should rename and deprecate as they recommend?
> 
> [1] [WICG/webcomponents#79 (comment)](https://github.com/WICG/webcomponents/issues/79#issuecomment-1159112560)

Side note on this point - @smaug---- [rightly pointed out](https://github.com/WICG/webcomponents/issues/79#issuecomment-1171245786) that because the new proposal returns a `StaticRange`, it can't do some of the convenient mutation things that a live `Range` can do. So I think we should keep with the existing proposal, which leaves `getRangeAt()` functionally the same.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/403#issuecomment-1208540087
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/403/1208540087@github.com>