Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

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?

  • 4 одговорa
  • 6 има овај проблем
  • 12 прегледа
  • Последњи одговор послао shanek

more options

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.

Сви одговори (4)

more options

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

more options

(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.

more options

Thanks so much. It worked!

more options

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.