Broken scrolling with Orca structural navigation in Firefox
Open
Nobody has claimed this yet.
bug
frontend
- Dominant language
- PHP
- Stars
- 1k
- Forks
- 198
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 29
Description
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
- I have read the CONTRIBUTING.md and followed the provided tips
- I accept that the issue will be closed without comment if I do not check here
- I accept that the issue will be closed without comment if I do not fill out all items in the issue template.
Explain the Problem
Structural navigation with Orca wraps around in Firefox much sooner than it should.
Steps to Reproduce
Explain what you did to encounter the issue
- Have a list of unread news items
- Try navigating between them using the Go to next heading command of Orca, e. g. the H key (the 1 for level 1 headings works too)
- Observe that after four normal and an additional fifth article the Orca navigation wraps around
System Information
- News app version: 5.0.2
- Nextcloud version: 30.0.2
- Cron type: Not relevant
- PHP version: Not relevant, it is a front-end issue
- Database and version: Not relevant, it is a front-end issue
- Browser and version: Firefox 132.0.2
- OS and version: current Arch Linux, but would be same on all Linux flavors
No errors in any logs, and surprisingly, this works in Chromium.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Firefox 132.0.2 with Orca using a list containing at least five unread articles, then inspect the front-end heading structure and navigation behavior. Done means Orca can move through all unread articles without wrapping prematurely, with the behavior checked against Chromium.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100