My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 140101: Setting and unsetting display:none obliterates current scroll position
4 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ka...@chromium.org
Closed:  Aug 2012
Cc:  eae@chromium.org, o...@chromium.org, jchaffraix@chromium.org, tkent@chromium.org, ligim...@chromium.org, kerz@chromium.org

Restricted
  • Only users with EditIssue permission may comment.


Sign in to add a comment
 
Reported by sc...@google.com, Aug 1, 2012
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
Aug 1, 2012
#1 levin@chromium.org
(No comment was entered for this change.)
Cc: eae@chromium.org o...@chromium.org
Labels: -Area-Undefined -OS-Windows Area-WebKit OS-All
Aug 1, 2012
#2 eae@chromium.org
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.
Aug 1, 2012
#3 jeffhar...@google.com
This is affecting the Google Chat team
Labels: Hotlist-GoogleApps
Aug 1, 2012
#4 tkent@chromium.org
http://trac.webkit.org/changeset/123637 seems a fix for this issue.

Cc: jchaffraix@chromium.org
Aug 3, 2012
#5 o...@chromium.org
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?
Status: Fixed
Owner: ka...@chromium.org
Aug 11, 2012
#6 tkent@chromium.org
 Issue 140802  has been merged into this issue.
Cc: tkent@chromium.org
Aug 11, 2012
#7 tkent@chromium.org
 Issue 137843  has been merged into this issue.
Cc: ligim...@chromium.org kerz@chromium.org
Aug 11, 2012
#8 tkent@chromium.org
(No comment was entered for this change.)
Labels: -Type-Bug -Pri-2 Type-Regression Pri-1 Mstone-21 Merge-Requested
Aug 15, 2012
#9 kar...@google.com
(No comment was entered for this change.)
Labels: -Merge-Requested Merge-Approved
Aug 15, 2012
#10 tkent@chromium.org
Merged to M21 branch: http://trac.webkit.org/changeset/125733

Labels: -Merge-Approved Merge-Merged
Oct 13, 2012
#11 bugdro...@chromium.org
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.
Labels: Restrict-AddIssueComment-Commit
Mar 9, 2013
#12 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Type-Regression -Area-WebKit -Mstone-21 Cr-Content Type-Bug-Regression M-21
Mar 13, 2013
#13 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Apr 5, 2013
#14 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Cr-Content Cr-Blink
Sign in to add a comment

Powered by Google Project Hosting