all out.
-- Dan
*From:*Di Zhang
*Sent:* Tuesday, March 25, 2025 4:42 PM
*To:* blink-dev
*Subject:* [EXTERNAL] [blink-dev] Intent to Ship: Selection
API getComposedRanges and direction
*Contact emails*
dizha...@chromium.org &
*Sent:* Tuesday, March 25, 2025 4:42 PM
*To:* blink-dev
*Subject:* [EXTERNAL] [blink-dev] Intent to Ship: Selection
API getComposedRanges and direction
*Contact emails*
dizha...@chromium.org <mailto:dizha...@chromium.org>
*Explainer*
None
the TAG may be able to help unblock some
>> of the disagreements that have caused the spec changes to stall out.
>>
>>
>>
>> -- Dan
>>
>>
>>
>> *From:* Di Zhang
>> *Sent:* Tuesday, March 25, 2025 4:42 PM
>> *To:* blink-dev
ions>
> for a TAG review. And in any case the TAG may be able to help unblock some
> of the disagreements that have caused the spec changes to stall out.
>
>
>
> -- Dan
>
>
>
> *From:* Di Zhang
> *Sent:* Tuesday, March 25, 2025 4:42 PM
> *To:* blink-d
out.
-- Dan
From: Di Zhang
Sent: Tuesday, March 25, 2025 4:42 PM
To: blink-dev
Subject: [EXTERNAL] [blink-dev] Intent to Ship: Selection API getComposedRanges
and direction
Contact emails
dizha...@chromium.org<mailto:dizha...@chromium.org>
Explainer
None
Specification
https://w3
Contact emails
dizha...@chromium.org
Explainer
None
Specification
https://w3c.github.io/selection-api/#dom-selection-getcomposedranges
Summary
This feature ships two new API methods for the Selection API: *
Selection.direction which returns the selection's direction as either
"none", "forward
