w3c/selection-api Issues

Last updated May 17, 2024, 5:56:45 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#4 Determine whether removeRange needs to check object equality or not ❌
#5 Determine whether deleteFromDocument should replace selection's range or not ❌
#11 Clarify relationship between selectstart/selectionchange and keyboard/mouse events ❌
#23 Parallel Selection-like object for concurrent editing? ❌
#26 Should we include the default result in the beforeSelectionChange Event? ❌
#28 Specify where the caret should be placed in the markup ❌
#65 Pass the original events or add events types in selectionchange ❌
#90 Specify when the selection collapsing happen on mouse click ❌
#103 Changing the selection creates a Range object ❌
#121 Add accessibility section ❌
#124 collapse and setBaseAndExtent methods contain redundant checks of offset ❌
#149 interop: Trailing whitespace in h1/h2 is selectable in firefox, not selectable in chrome ❌
#163 Serialization of the current selection, when that selection crosses shadow roots ❌
#167 getSelection().addRange should allow range with both boundary points in shadow tree ❌
#173 Clarify how `selection.modify()` when the granularity parameter is `paragraph` handles non-editable elements in an editing host ❌
#174 Migrate away from "queue a task" ❌
#175 Define to remove selection range automatically if a selection range is modified into different selection root ❌