Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694) from Peter Linss on 2022-02-08 (public-webapps-github@w3.org from February 2022)

From: Peter Linss <notifications@github.com>
Date: Mon, 07 Feb 2022 17:01:28 -0800
To: w3ctag/design-reviews <design-reviews@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3ctag/design-reviews/issues/694/1032103692@github.com>

Took a look at this today with @LeaVerou and @maxpassion, we were wondering what the purpose was of adding `getComposedRange` vs overloading `getRangeAt` to accept the ComposedRangeOptions. As far as we could tell the only apparent difference is the result of a live Range vs a StaticRange, which seems like an orthogonal issue.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/694#issuecomment-1032103692
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/694/1032103692@github.com>

Received on Tuesday, 8 February 2022 01:01:41 UTC