Closed
Bug 1749677
Opened 2 years ago
Closed 2 years ago
Check whether we should handle untrusted keypress event for input elements
Categories
(Core :: DOM: Core & HTML, task)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
105 Branch
Tracking | Status | |
---|---|---|
firefox105 | --- | fixed |
People
(Reporter: edgar, Assigned: avandolder)
Details
(Keywords: good-first-bug)
Attachments
(1 file)
This is a follow-up of https://phabricator.services.mozilla.com/D135464#inline-745964.
We don't handle enter keypress event after bug 1695636. This bug is filed to check whether we need to handle other keypress events and add wpt tests for them
Updated•2 years ago
|
Keywords: good-first-bug
Reporter | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → avandolder
Assignee | ||
Comment 2•2 years ago
|
||
Assignee | ||
Comment 3•2 years ago
|
||
Neither Chrome nor Safari trigger change, focus, or input events for untrusted keypresses on radio buttons and ranges, so I've added a check for that along with additional test cases.
Pushed by avandolder@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f65be8c461b Do not trigger change, input, or focus events on untrusted keypress events for input elements. r=edgar
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/35515 for changes under testing/web-platform/tests
Comment 6•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox105:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•