You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Shadow Selection API enables both querying and setting the document-wide selection across shadow boundaries. Currently, all browsers demonstrate divergent behavior when using the existing getSelection() API on a composed tree.
The API includes a single new API (getComposedSelection()) and backwards-compatible changes to a number of APIs (like setBaseAndExtent().
There is consensus on the shape of the API, but no spec or implementations.
Rationale
Selection does not work across or within shadow roots. This makes fully-featured rich-text editors impossible to implement with web components. Some of the web's most popular editors have issues that are blocked on this functionality:
In practice we'd hope to see proposals that are already on a standards track, or at the very least are clearly on that path, before the proposals selection period, which is now.
Thank you for proposing Composed Selection for inclusion in Interop 2023.
We wanted to let you know that this proposal was not selected to be part of Interop this year. The web standard for this technology, along with the appropriate tests, have not yet reached a point where inclusion in the Interop project makes sense. Resubmitting a proposal for this feature as part of a future round of Interop would be welcome.
For an overview of our process, see the proposal selection summary. Thank you again for contributing to Interop 2023!
Description
The Shadow Selection API enables both querying and setting the document-wide selection across shadow boundaries. Currently, all browsers demonstrate divergent behavior when using the existing
getSelection()
API on a composed tree.The API includes a single new API (
getComposedSelection()
) and backwards-compatible changes to a number of APIs (likesetBaseAndExtent()
.There is consensus on the shape of the API, but no spec or implementations.
Rationale
Selection does not work across or within shadow roots. This makes fully-featured rich-text editors impossible to implement with web components. Some of the web's most popular editors have issues that are blocked on this functionality:
Specification
Tests
I can't find tests for the latest API definition; should write some --
The text was updated successfully, but these errors were encountered: