Open Bug 1760319 Opened 4 years ago Updated 2 years ago

Lost in page navigation

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Firefox 98
defect

Tracking

()

UNCONFIRMED

People

(Reporter: ddw.256, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

In a longish page, after several page downs via the spacebar key (repeatedly), followed by a subsequent down arrow.

Actual results:

The focus (ie page) then reverts back up closer to the top of the page, rather than continuing down the page by a smaller increment.

Expected results:

The focus should have continued down the page but by a smaller increment.

It's as if a page location pointer was deleted before the down arrow command was executed, resulting in a redirection to an unwanted part of the page.

It occurred in the New York Times article https://messaging-custom-newsletters.nytimes.com/template/oakv2?campaign_id=9&emc=edit_nn_20220318&instance_id=56102&nl=the-morning&productCode=NN&regi_id=186518559&segment_id=85903&te=1&uri=nyt%3A%2F%2Fnewsletter%2Fe4c7df77-35ff-5b69-8473-a882bca992b6&user_id=49bf693b9d2a1a645701cc313bc03390

I have noticed this happening on occasion, particularly on longer pages where more navigation has occurred, and on other web sites.

Lenovo T450 running Linux Mint 20.3 Cinnamon 98.0.1 Firefox.

Happy hunting and TIA.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: UI Events & Focus Handling
Product: Firefox → Core

Sounds reasonable to me that the bug is in the UI.

When several spacebar-page downs are followed by a down error and the focus reverts back up the page much closer to the top, then we have a problem.

TIA.

Not really happy with setting this at this low severity, but that's where the defect severity definition puts it.

Would you disagree :hsinyi?

Severity: -- → S4
Flags: needinfo?(htsai)
Flags: needinfo?(hsivonen)

(In reply to Andreas Farre [:farre] from comment #3)

Not really happy with setting this at this low severity, but that's where the defect severity definition puts it.

Would you disagree :hsinyi?

Yup, S4/S3 sounds good to me. I didn't manage to reproduce it after several trials. We may want to bump the priority with a reliable STR and more frequency.

Flags: needinfo?(htsai)
You need to log in before you can comment on or make changes to this bug.