Closed
Bug 1992770
Opened 9 months ago
Closed 8 months ago
[A11y][Keyboard Navigation] Unexpected keyboard navigation order when tabbing through the inserted elements and attached comments
Categories
(Firefox :: PDF Viewer, defect, P1)
Tracking
()
People
(Reporter: danibodea, Assigned: calixte)
References
Details
(Keywords: access)
Attachments
(2 files)
Note
- After inserting any elements to a PDF document and attaching comments to them, tapping the TAB key will first focus the inserted elements and only afterwards will it focus on the comments.
Found in
- Nightly v145.0a1
Affected versions
- Nightly v145.0a1
Tested platforms
- Affected platforms: all
- Unaffected platforms: none
Steps to reproduce
- Load a PDF document.
- Insert any elements and attach comments.
- Close the dialogs (Comments Sidebar, Signature, Highlights, Text insertion, Drawing, Image insertion)
- Click in the top of the document.
- Press TAB multiple times to navigate through the inserted elements and their comments.
Expected result
- Keyboard navigation goes through the inserted elements AND their comments in top-down order.
Actual result
- Firstly, keyboard navigation goes through the inserted elements, when it reaches the last one it will move to the last one's comment icon, then move upwards to the previous comment icon in the page untill it reaches the first comment icon.
Regression range
- This is not a regression as this feature is still in the implementation phase. A worse behavior was observed before this.
Additional notes
- This issue also occurs if various types of inserted elements with comments are created before testing.
- This issue will no longer reproduce after saving the PDF document locally.
| Reporter | ||
Updated•9 months ago
|
| Reporter | ||
Updated•9 months ago
|
Summary: [A11y][Keyboard Navigation] Unnexpected keyboard navigation order when tabing through the inserted elements and attached comments → [A11y][Keyboard Navigation] Unexpected keyboard navigation order when tabbing through the inserted elements and attached comments
| Assignee | ||
Updated•9 months ago
|
Assignee: nobody → cdenizet
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P1
Comment 1•9 months ago
|
||
Updated•9 months ago
|
Accessibility Severity: --- → s3
Updated•8 months ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → 145 Branch
Updated•8 months ago
|
QA Whiteboard: [QA-4345][qa-found-in-c145][S3] → [QA-4345][qa-found-in-c145][S3][qa-triage-done-c146/b145][qa-ver-needed-c146/b145]
Flags: qe-verify+
| Reporter | ||
Comment 2•8 months ago
|
||
This fix has been verified in Windows 10, MacOS 14.7.1 M1 and Ubuntu 24 ARM. Keyboard navigation works in top-down order, as expected.
| Reporter | ||
Updated•8 months ago
|
QA Whiteboard: [QA-4345][qa-found-in-c145][S3][qa-triage-done-c146/b145][qa-ver-needed-c146/b145] → [QA-4345][qa-found-in-c145][S3][qa-triage-done-c146/b145][qa-ver-done-c146/b145]
You need to log in
before you can comment on or make changes to this bug.
Description
•