The user cannot use keyboard navigation to move foxus backwards to the Theme or the Text and layout buttons from Reader View mode
Categories
(Toolkit :: Reader Mode, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox132 | --- | wontfix |
| firefox133 | --- | verified |
| firefox134 | --- | verified |
People
(Reporter: danibodea, Assigned: Gijs)
References
(Regressed 1 open bug, Regression)
Details
(Keywords: access, regression)
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Note
- When in Reader View mode, the user cannot use keyboard navigation (SHIFT+TAB) to move focus upwards from the Read Aloud button to the Theme button, or to the Text and layout button from the Reader View mode.
Found in
- Beta v132.0 (RC)
Affected versions
- Beta v132.0 (RC)
- Nightly v133.0a1
Tested platforms
- Affected platforms: Windows 10, MacOS 11.
- Unaffected platforms: ?
Steps to reproduce
- Load a webpage that supports Reader View mode:
ex. https://en.wikipedia.org/wiki/Main_Page - Enable Reader View mode.
- Using keyboard navigation navigate forward beyond the Theme button (using TAB key).
- Using keyboard navigation navigate to the Theme button, or the Text and layout button (using SHIFT+TAB hotkey).
Expected result
- The user is able to move focus on the Theme button and the Text and layout button.
Actual result
- The user is NOT able to move focus on the Theme button and the Text and layout button.
Regression range
- Potentially regressed by: bug 1909885
Bug 1909885 - Add shift tab listeners for reader mode narrator, theme menu, and text menu. r=Gijs
Remove redundant lines, fix test to correctly check focus in text layout menu
Differential Revision: https://phabricator.services.mozilla.com/D220969
Comment 1•1 year ago
|
||
:sandy.chu.40, since you are the author of the regressor, bug 1909885, could you take a look?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
Comment 5•1 year ago
|
||
The patch landed in nightly and beta is affected.
:Gijs, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox133towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 6•11 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D227097
Updated•11 months ago
|
Comment 7•11 months ago
|
||
beta Uplift Approval Request
- User impact if declined: broken focus behaviour in reader mode
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: See comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: small patch, has automated test, early beta cycle
- String changes made/needed: no
- Is Android affected?: no
| Assignee | ||
Updated•11 months ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Updated•11 months ago
|
| Reporter | ||
Comment 9•11 months ago
|
||
It would appear that the current issue was fixed, but another regression is uncovered: bug 1928433.
@Gijs: Can you check it out?
| Assignee | ||
Comment 10•11 months ago
|
||
(In reply to Daniel Bodea [:danibodea] from comment #9)
It would appear that the current issue was fixed, but another regression is uncovered: bug 1928433.
@Gijs: Can you check it out?
Thanks, I will check in that bug (where bugbot also gave me a needinfo. :-) )
| Reporter | ||
Comment 11•11 months ago
|
||
I can confirm this fix in Nightly v134.0a1 and Beta v133.0b2 in Windows 10, Unbuntu 22 and MacOS 11.
Considering the regression mentioned in comment 9, I will close this report. Thank you.
| Reporter | ||
Updated•11 months ago
|
Updated•11 months ago
|
Description
•