Windows 10 bereikte EO (einde ondersteuning) op 14 oktober 2025. Als je Windows 10 gebruikt, lees dan dit artikel.

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info
Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.
Gearchiveerd

Page-down and Page-up keys are going straight down to the bottom of the page, home and end keys don't work right, and once at the bottom, can't scroll up using those keys. Any idea?

revan1013

Page-down and Page-up keys are going straight down to the bottom of the page, home and end keys don't work right, and once at the bottom, can't scroll up using those keys. Any idea?

It does not happen on other software.

Page-down and Page-up keys are going straight down to the bottom of the page, home and end keys don't work right, and once at the bottom, can't scroll up using those keys. Any idea? It does not happen on other software.

Alle antwoorden (4)

Try hitting F7. You probably inadvertently activated Caret browsing.
http://kb.mozillazine.org/Accessibility.browsewithcaret

(your More system details list confirm: accessibility.browsewithcaret is true)


Your above posted system details show multiple Java Console extensions.
You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.

See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions


Your above posted system details show outdated plugin(s) with known security and stability risks that you should update.

  • Shockwave Flash 10.0 r45

Update the Flash plugin to the latest version.

Thanks so much. It worked!

It just happened to me in Firefox 5. Caret browsing was NOT on. But I turned it on, and then turned it off again, and it worked fine. This seems to be a bug.