Closed
Bug 1733223
Opened 3 years ago
Closed 3 years ago
Fire READONLY state change events.
Categories
(Core :: Disability Access APIs, task, P3)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
95 Branch
Tracking | Status | |
---|---|---|
firefox95 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
Attachments
(1 file)
Many roles/elements have a hardcoded READONLY state for their lifetime. aria-readonly
changes already work. Things that still need to be verified/implemented:
- Need to fire event for
readonly
attribute changes ininput
elements. - For ARIA roles with a eReadonlyUntilEditable, need to make sure we are observing editable changes, and firing readonly changes when editable changes.
Assignee | ||
Comment 1•3 years ago
|
||
Changing severity to S3 because this is ongoing cache the world work that does not affect current users.
Severity: -- → S3
Type: defect → task
Priority: -- → P3
Assignee | ||
Comment 2•3 years ago
|
||
This patch also adds tests for other READONLY/EDITABLE state changes
that already work.
Updated•3 years ago
|
Assignee: nobody → eitan
Status: NEW → ASSIGNED
Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a4501a0f8f59
Fire READONLY state change when input gets readonly attribute. r=morgan
Comment 4•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox95:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•