182935 - Pressing Home key does not move to top of page

Status: VERIFIED INVALID

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Christos Cheretakis]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021126

When scrolling thru the page and then pressing Home to get back to the top,
mozilla does not move to top of page, but a little bit below. Will attach
screenshot of location after pressing Home.

Reproducible: Always

Steps to Reproduce:
1. Go to page
2. Move down
3. Press Home to get back to the top

Actual Results:  
mozilla scrolls back to some point near the top of the page, but not to 0,0

Expected Results:  
Moved to top of page

Comment 1

[Christos Cheretakis]

Attachment: Screenshot after Home

Comment 2

[Christos Cheretakis]

Missing 1.2 in Version listbox... That's the version of mozilla where it happens.

Comment 3

[Chris Lyon]

WFM 20021130 on WinXP.

In your screenshot, it looks like the image link has focus (the dotted rectangle
around it).  Does the same thing happen if it doesn't have focus?

Comment 4

[Christos Cheretakis]

Additional step required: mozilla needs to be in caret-browsing mode.
It must have entered it earlier without me noticing it. Anyways...

The image gets the focus after pressing Home.

Comment 5

[Chris Lyon]

->Keyboard Nav

Comment 6

[R.K.Aa.]

This bug is probably invalid. See bug 143996:

In caret-browsing mode, home/end should go to start/end of a line and not to
start/end of the page.

Comment 7

[Chris Lyon]

agreed

Comment 8

[Christos Cheretakis]

There are, however, image links that are rendered before the one that gets the
focus when pressing Home. If mozilla does not move to the start of a line that's
currently in view (or the cursor is already in), why shouldn't it move to the
top-most/first beginning of line?

Comment 9

[Chris Lyon]

That's a good point Christos, but I think that as pointed out in bug 143996, the
Home button behavour is broken.  Since the correct behaviour is the one
described in that bug, keeping this one open serves no purpose.

Once that bug gets fixed this one would be invalid anyway.

Comment 10

[sairuh (rarely reading bugmail)]

v