Closed Bug 507171 Opened 17 years ago Closed 2 years ago

consider focussing the contentarea before page loads fully (when triggering pageload from location bar)

Categories

(Camino Graveyard :: Accessibility, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: hhaamu, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.11) Gecko/2009060219 Camino/2.0b3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.11) Gecko/2009060219 Camino/2.0b3 After pressing "enter" on the location bar, the content area isn't immediately focussed, but the focus lingers in an unknown place. IMO, the focus should move to the content area the moment I press enter. Many pages have a external script or similar residing on a slow server. Until the script is loaded, the content area doesn't have focus, and I must manually focus it (with the mouse! tabbing doesn't seem to work) to scroll it. Reproducible: Always Steps to Reproduce: 1. Go to URL 2. Try to scroll with arrow keys/pgdn before it has fully loaded Actual Results: Many instances of beeps telling me my keystroke was invalid. Expected Results: Page scrolls on keyboard input. Page does not require an explicit mouse-click to focus on content area.
Blocks: 383871
( I see a different behaviour here, depending if I test with my home-made build [GCC4.2, 10.5SDK] or the official build. Official builds: after hitting enter, the focus goes 'somewhere', as described in comment 0. Home-made build: the location bar remains focussed while the page is loading ) Tested by copy/pasting the url, 2.0b4pre and 2.1a1pre builds
Possibly; it depends on what happens with the ChildViews during pageload, and whether they would keep focus.
On the flip side, the contentarea steals focus from the location bar when the page finishes loading.
Can you re-test this with the latest nightly (2.1a1pre) builds? I see the same behaviour in Safari 5 and our latest nightlies -- holding down, e.g., the arrow key while the page is loading results in scrolling in both browsers.
Never mind; step 1 in comment 0 should be "type or paste URL into location bar". Clicking a link doesn't have the same results (and, in fact, works). There's definitely something wonky here that we should fix if at all possible.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I wonder if this is actually a dupe of that old bug pink partially fixed? (All I can find right now is bug 175701, but this is the opposite of that.) At any rate, pageload from the location bar is the odd-man-out here, since everything else (bookmarks, bookmark bar, content link-click) appears to focus as soon as we start to have content. Except maybe the @#$#@4 autocomplete window, but that's hard to tell (and it's focus-buggy as-is).
Summary: consider focussing the contentarea before page loads fully → consider focussing the contentarea before page loads fully (when triggering pageload from location bar)
(In reply to comment #7) > Except maybe the @#$#@4 autocomplete window Yeah, clicking in the autocomplete window also triggers this issue. But note that when the autocomplete window comes up, it doesn't remove the focus from the location bar.
(In reply to comment #7) > I wonder if this is actually a dupe of that old bug pink partially fixed? (All > I can find right now is bug 175701, but this is the opposite of that.) I was thinking of bug 191145 (or possibly conflating the two, or possibly of some other bug which I confused with bug 191145), and the answer is no, not a dupe of that one, at least ;)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.