Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 140101 Setting and unsetting display:none obliterates current scroll position
Starred by 4 users Reported by scali@google.com, Aug 1 2012 Back to list
Status: Fixed
Owner:
User never visited
Closed: Aug 2012
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Regression

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
Chrome Version       : 20.0.1132.57
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: FAIL (in a different flavor)
  Firefox 4.x: OK
     IE 7/8/9: WHO CARES

What steps will reproduce the problem?
1. Open the HTML file in question
2. Scroll down in the given element until you're midway though
3. Click the "hide" button, then the "show" button.
4a. Using the mousewheel, scroll down.
4b. Alternatively, put focus in the div by clicking, then hit the down arrow key.

What is the expected result?
I scroll down from where I was before I set display:none.

What happens instead?
The scrollbar shoots to the top, then scrolls down.  (Note in Safari, when I unhide the element, the scrollbar is already at the top).

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11

 
derp.html
922 bytes View Download
Comment 1 by levin@chromium.org, Aug 1 2012
Cc: ojan@chromium.org e...@chromium.org
Labels: -Area-Undefined -OS-Windows Area-WebKit OS-All
Comment 2 by e...@chromium.org, Aug 1 2012
Could you give an example of where this is causing problems? Is it breaking an app/web page or is it blocking a use-case for you? Just trying to understand why this might be needed.
Labels: Hotlist-GoogleApps
This is affecting the Google Chat team
Comment 4 by tkent@chromium.org, Aug 2 2012
Cc: jchaffraix@chromium.org
http://trac.webkit.org/changeset/123637 seems a fix for this issue.

Comment 5 by ojan@chromium.org, Aug 4 2012
Owner: karen@chromium.org
Status: Fixed
I've confirmed this doesn't happen on ToT. We should probably make sure http://trac.webkit.org/changeset/123637 gets merged into M21. It's too late for M20, right?
Comment 6 by tkent@chromium.org, Aug 11 2012
Cc: tkent@chromium.org
 Issue 140802  has been merged into this issue.
Comment 7 by tkent@chromium.org, Aug 11 2012
Cc: ligim...@chromium.org kerz@chromium.org
 Issue 137843  has been merged into this issue.
Comment 8 by tkent@chromium.org, Aug 11 2012
Labels: -Type-Bug -Pri-2 Type-Regression Pri-1 Mstone-21 Merge-Requested
Comment 9 by kareng@google.com, Aug 16 2012
Labels: -Merge-Requested Merge-Approved
Comment 10 by tkent@chromium.org, Aug 16 2012
Labels: -Merge-Approved Merge-Merged
Merged to M21 branch: http://trac.webkit.org/changeset/125733

Project Member Comment 11 by bugdroid1@chromium.org, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 12 by bugdroid1@chromium.org, Mar 9 2013
Labels: -Type-Regression -Area-WebKit -Mstone-21 Cr-Content Type-Bug-Regression M-21
Project Member Comment 13 by bugdroid1@chromium.org, Mar 14 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member Comment 14 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Sign in to add a comment