Bug 22558 - Incorrect scroll position and scrollbar behavior after clicking an anchor link
Summary: Incorrect scroll position and scrollbar behavior after clicking an anchor link
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://kirinyale.d-world.org/test/pag...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-29 14:19 PST by Andrey Antsut
Modified: 2009-12-30 11:18 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Antsut 2008-11-29 14:19:58 PST
Tested in 1280x1024 resolution.

Steps to reproduce:
1. Open URL.
2. Click link marked with "Click here!" (the only link on this test page).
3. Observe page and scrollbar.

Actual results:
1. Page is scrolled more than allowed by CSS settings of its content.
2. Thumb position on scrollbar is incorrect and does not allow to scroll back to top of the page. This is not fixed even by pressing the "back" button in browser.

Expected results:
1. Visible bottom of the page should never be lower than it is possible to reach with manual scrolling (without clicking the link).
2. Scrollbar should be drawn with proper position and should allow scrolling to the beginning of the page.

Tested in browsers:
Google Chrome 0.4.154.25 - FAIL
Safari 3.2.1 - FAIL
Webkit latest nightly build - FAIL
Internet Explorer 6 - OK except the page is not scrolled at all after clicking the link
Firefox 3.03 - OK
Opera 9.62 - OK

P.S. Test page is based on a real page which is still under construction, thus images are not included on server (they are not relevant for this issue). I have been unable to reproduce this with a more simple CSS design by now; most probably it has something to do with overuse of <div> layers with relative positioning, embedded inside another <div> with limited size (to remove extra blank scrolling).
Comment 1 Jerome Leclanche 2009-12-30 11:18:52 PST
Is this a dupe of bug 20429?