Intent to Prototype: Selection API across Shadow DOM and Selection.getComposedRanges

[Di Zhang]

Contact emailsdizh...@chromium.org

Explainerhttps://github.com/mfreed7/shadow-dom-selection#readme

Specificationhttps://w3c.github.io/selection-api

Summary

The Selection API draft now includes specifications about behaviors when selecting across shadow DOM. https://w3c.github.io/selection-api/ This includes new: * Selection.direction * Selection.getComposedRanges()

Blink componentBlink>DOM>ShadowDOM

Motivation

Shadow DOM is now supported across all major rendering engines. We should update the Selection API so users can select across shadow boundaries and see interoperable behaviors. The new changes include API support for multiple ranges across a composed tree.

Initial public proposalNone

TAG reviewNone

TAG review statusNot applicable

Risks

Interoperability and Compatibility

None

Gecko: Positive (https://groups.google.com/a/mozilla.org/g/dev-platform/c/zF7soLapT-Y) Currently in development.

WebKit: Shipped/Shipping (https://github.com/WebKit/WebKit/pull/10843#issuecomment-1592149737) Partially shipped new API

Web developers: Positive (https://stackoverflow.com/questions/62054839/shadowroot-getselection)

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Debuggability

None

Is this feature fully tested by web-platform-tests?No

Flag name on chrome://flagsNone

Finch feature nameNone

Non-finch justificationNone

Requires code in //chrome?False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5971377218912256?gate=5903244307202048

This intent message was generated by Chrome Platform Status.