Broken scrolling with Orca structural navigation in Firefox
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- accessibility, frontend
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.
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.
- Dominant language
- PHP
- Stars
- 1k
- Forks
- 200
- Avg merge
- 20h 28m
- Merged PRs (30d)
- 32
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from nextcloud/news
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
replace mkdocs with somethingMay be free again @Grotax claimed this 95 days ago, and no pull request is open. Open
nextcloud/news#3887 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
bug help wanted upstream
Difficulty 3/5 1-2 days Newbie friendliness 58/100
nextcloud/news#3840 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Old /download.php attachment links: redirect drops the subfolder, nginx.example.conf returns 404OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
wpgenius/stackfolio#22 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Automattic/static-site-importer#3024 ·
Maintainers usually reply within 1 day