Should onselectstart and onselectionchange have content attributes or just IDL attributes?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Read the Selection API section “Extensions to GlobalEventHandlers” and compare its IDL-only wording with the Chromium interoperability report linked in the issue. Check the provided HTML example across the relevant browser behavior, then clarify whether onselectstart and onselectionchange should have content attributes as well as IDL attributes; done means the specification has an explicit, interoperable resolution.
Written by the indexing model from the issue text.
Description
The spec currently lists IDL attributes for onselectstart and onselectionchange here: https://w3c.github.io/selection-api/#extensions-to-globaleventhandlers
Someone found the onselectionchange content attribute is not currently interoperable between browsers. Consider the following:
<div id=parent onselectionchange="console.log('parent onselectionchange')">
<input onselectionchange="console.log('input onselectionchange')">
</div>
Firefox and Safari will attach selectionchange event listeners for both elements, but chrome does neither. I'd be happy to implement this in chrome if the spec is updated to explicitly say that we should have global onselectionchange content attributes in addition to IDL attributes.
I suspect that onselectstart has the same interop issue right now.
- Dominant language
- HTML
- Stars
- 49
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from w3c/selection-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
w3c/selection-api#354 ·
-
Agenda+
Difficulty 3/5 1-2 days Newbie friendliness 48/100
w3c/selection-api#361 · 2 comments ·
-
w3c/selection-api#358 · 2 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
w3c/selection-api#355 ·
-
the steps of Selection.extend() does not check whether the given offset is valid in the container Open
Difficulty 1/5 Under an hour Newbie friendliness 55/100
w3c/selection-api#353 · 1 comment ·
All issues in w3c/selection-api
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100