Accessibility: Subject field accessible name is never updated after the initial opened mail
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Accessibility Severity:s3)
People
(Reporter: MarcoZ, Assigned: aleca)
References
(Regression)
Details
(Keywords: access, regression)
Attachments
(1 file, 1 obsolete file)
1.75 KB,
patch
|
mkmelin
:
review+
|
Details | Diff | Splinter Review |
STR:
- Open TB.
- Turn off preview pane. I have it turned off because I want messages to stay unread when arrowing onto them, and only get marked read if I open them with Enter.
- Open the first mail.
- The accessible name of the mail-headerfield with ID "expandedsubjectBox" receives an accessible name of "Subject: " followed by the actual subject.
- Close the mail with CTRL+W.
- Select a different mail and open it.
- Inspect the accessible name for the subject header field.
- Expected: The field should read "subject" followed by the new subject.
- Actual: The accessible name still shows the subject for the previous mail from step 3.
- Close and open more e-mails.
- Result: The accessible name for the subject header field never gets updated.
Other fields such as from and to are not affected by this bug.
I suspect that something in the implementation of bug 1493608 never works beyond the first opened mail.
Setting accessibility severity to 3 in accordance with the Accessibility triage guidelines.
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
(The implementation was bug 1589859)
Alex, I guess this is because we're re-using these fields and not creating new ones. We could either generate them always, or then we need to store the aria-labelledby value we used before we remove it.
Reporter | ||
Comment 2•5 years ago
|
||
Again, the other fields work, only the subject field doesn't get updated. Perhaps you need to actually set the aria-labelledby again somewhere once you reuse the field? I tried tinkering with this in msgHeaderView.js, but even if I update the aria-labelledby in both the case of a new or existing field once it is all set up, it doesn't work in my local build.
Assignee | ||
Comment 3•5 years ago
|
||
Thanks for the detailed report.
I'll work on it.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Apparently, the subject field is not recreated when a new message pane is opened, even if the previous one is closed.
Since we were removing the aria-labelledby
attribute to prevent hierarchy issues with the dynamically set aria-label
, that attribute wasn't available anymore in any other message panel, therefore the previous value set in the subject aria was remaining.
I fixed the issue by fetching the value from the label[control="id"]
element, which we don't need to remove.
The other fields don't present this problem since are dynamically generated.
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Sounds good, thanks for the review and suggestion. I'll fix this right away
Assignee | ||
Comment 7•5 years ago
|
||
Comment 8•5 years ago
|
||
Updated•5 years ago
|
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/1950b809c989
Fix aria-label not updating the Subject field in the message header. r=mkmelin
Updated•1 years ago
|
Description
•