MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
Should we fire a HighlightRangePointerEvent on the Range that was hit, instead of the containing HighlightRangeGroup?
@sanketj is already working on this.
Since Jan 8, 2020.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
The benefit of making Range an EventTarget and firing the event on the Range object directly is that the HighlightRangePointerEvent would not need to maintain a special Range pointer internally - the hit range can be obtained via the event's target property.
On the other hand, unless we define a new event path from Range objects to their containing HighlightRangeGroups, web developers would need to create one event listener per Range in order to listen for the event on an entire group. If the event is fired on the HighlightRangeGroup instead, developers can just create a single listener on the group, which seems more convenient.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.