Closed Bug 1716276 Opened 3 years ago Closed 3 years ago

PgUp works like Home, arrows do not work

Categories

(Firefox :: Keyboard Navigation, defect)

Firefox 89
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: michele.costabile, Unassigned, NeedInfo)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

On some sites, navigation with cursor keys is broken. Paging up in a long page brings at the top.

Actual results:

Open a page, like https://en.wikipedia.org/wiki/Memory_paging. Pressing PgDn does not scroll before a clic inside the content area. After that, repeatedly paging up and down, scrolling down from the top scrolls one line first, one page after.

Open a page at www.ilpost.it. Scrolling down has the same incorrect behavior, while PgUp, or arrow up, brings the page home, no matter where you are.

Expected results:

paging should be active when page loads and should behave as expected.

The Bugbug bot thinks this bug should belong to the 'Firefox::New Tab Page' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → New Tab Page

Hello Michele!

I have tried to reproduce the issue using Firefox 89.0 with Windows 10 but unfortunately I wasn't able to reproduce the issue.
Could you please answer the following question in order to further investigate this issue?

  1. Could you please attach a video or a screenshot with the issue?
  2. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
  3. Does this issue happen with the latest nightly build? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
  4. Do you have any add-ons installed? If so could you please list them?
Flags: needinfo?(michele.costabile)

I tried to boot Firefox with a brand new account. And keyboard navigation was OK. I logged into Firefox and it stopped working, so it is definitely something in my account.

I tried logging out and removing the Facebook container extension. Restarting Firefox with the new profile, it still has the bug.
I still have the Forcepoint Endpoint extension, that I cannot remove, because this is a company managed machine.
Regarding plugins, I only have the OpenH264 and Widevine codecs.
I enclose troubleshooting information.

Flags: needinfo?(michele.costabile)

I tried restarting Firefox in troubleshoot mode, but this does not solve the problem. As soon as I have logged backinto Firefox, I could not recover the original situation.

I have a new installation, I did not log into Firefox and, whe offered to clean up previous data, I have accepted.
So far, everything is fine. I have a copy of about:support in this state and in the bugged state.
In my previous attempt, creating a new profile was helpful, but as soon as I logged into Firefox, the bug was back. So, it is somewhere in my profile, but I have no idea of what to look for.

Not sure what component this belongs to, does not sound like a New Tab bug.

Component: New Tab Page → Untriaged

Hello Michele! Sorry for the long reply time.

Could you please attach the about:support for the bugged state and the normal one please so we can look into this?

Thank you!

Flags: needinfo?(michele.costabile)

I took a long time to answer, sorry. I am enclosing a copy of about:support in the before state (correct) and the after state (bugged).
To test the bug, please navigate to ilpost.it. Not all size paginate incorrectly with this setup.
The problem I experience is that PgUp and arrow up behave like Home.
I made a text comparison and found something different in the accessibility section. I did not setup accessibility in my browser and have no special needs.

I found a way to get back to a working state. I opened about config and looked for edited preferences. I reset to default accessibility.browsewithcaret and accessibility.typeaheadfind.flashBar and I got back to a working state.
I guess accessibility values are stored into the profile, since the bruwser started behaving unexpectedly since my login.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Component: Untriaged → Keyboard Navigation
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: