5

Note: this is strictly Firefox question, as I have way too many addons to switch. However, if you know if I can do it in the other browser, your posts are welcome as well.

I am trying to switch to completely mouseless internet browsing (as much as this is possible). The problem is that my current workflow is somehow incompatible with the capabilities of the Firefox (at least as far as I know).

What I know and use to navigate on the page:

  • Tab and Shift-Tab to navigate between the links
  • F7 to enable/disable caret
  • Space, Shift-Space, PgUp,PgDown to scroll down/up

I also use extensively Shift with DOWN/UP/LEFT/RIGHT to select text, and Ctrl-Enter to open links in the new tab.

The problem:

I open a long page, say, a very long blog post, or a page with many not interesting sections on the top (with caret browsing i.e. F7 switched off - I only activate it occasionally). I quickly scroll with either Space or PgDown or ARROW_DOWN to the middle of the page.

Now, I want to focus some link. When I press Tab or F7, the browser starts navigating from the beginning of the page. If there are tens of links, it takes a while. Moreover, the view gets scrolled to the top, which hurts my flow.

Question:

Any hidden shortcuts, add-ons etc. so that upon entering the page and scrolling down, Tab focuses first link in my viewport instead of first on the page, or F7 puts the caret where I am now?

Workaround:

I know I can start with F7 (or in fact, a mix Tab to focus some area and then F7 to get the caret, because in some layouts F7 behaves weirdly) and scroll down using ARROW_DOWN, but it's much slower than scrolling with Space or PgDown.

Solution for scrolling with Space or PgDown while F7 is disabled will be preferred.

Edit: another alternative

It seems that Firefox quick search feature (/) and especially quick search in links only (') can help to get focus to some particular place, and then move on with the caret the normal way with F7 and arrow.

jakub.g
  • 4,904

1 Answers1

2

I am offering this as an answer rather than a comment because the current "answer" is that it can't be done and it is known bug in Firefox.

As I have been bothered by this same problem forever this question rekindled by obsession with it. So, I have been looking over at the Firefox Bugzilla page and it turns out that this problem was initially reported as a bug back in May of 2002!!! It is still open with discussion about solutions, patches that have been added and then backed out and numerous other bugs classified as duplicates (other manifestations) of this one.

The Bugzilla Log is HERE

Arbalest
  • 163
  • 8