Bug Tracker

#13437 closed bug (notabug)

Opened February 11, 2013 10:35PM UTC

Closed February 18, 2013 05:06PM UTC

Rendering error covers entire screen with scrollbar

Reported by: samuel6@pdx.edu Owned by: samuel6@pdx.edu
Priority: undecided Milestone: None
Component: unfiled Version: 1.9.0
Keywords: Cc:
Blocked by: Blocking:
Description

After dynamically adding a DOM element that increases the vertical scroll of a page, then removing it, the scrollbar renders wrong and covers the entire page.

This only happens in Chrome (I'm using the newest version).

You can repeat the issue easily by downloading http://pastebin.com/wB6pMzhw as a .html file, launching it, then clicking 'Create' followed by 'Destroy'. The issue is also mentioned here: http://stackoverflow.com/questions/14498552/white-box-in-chrome-covers-page/14822132#14822132.

This is my first bug report, so if you need more information let me know.

Attachments (0)
Change History (5)

Changed February 11, 2013 10:54PM UTC by anonymous comment:1

I should note a few things more.

1) I'm using Windows 7

2) My Chrome version is 24.0.1312.56 m

3) This only occurs when chrome is maximized

4) My screen resolution is 1280 x 1024

5) I can reproduce the error on other Windows boxes

Sorry about hastily making the ticket.

Changed February 12, 2013 03:17AM UTC by dmethvin comment:2

owner: → samuel6@pdx.edu
status: new → pending

There's not a lot of jQuery there. Can you create a test case with plain DOM and verify that the problem only occurs when the work is done by jQuery?

Changed February 12, 2013 03:43AM UTC by anonymous comment:3

Replying to [comment:2 dmethvin]:

There's not a lot of jQuery there. Can you create a test case with plain DOM and verify that the problem only occurs when the work is done by jQuery?

Yes, and you know what I tried repeating this on another machine and got no luck, not even one with the same resolution monitor. I'm going to try to create a test case that works on every resolution/Windows box. Thanks for looking into this.

Changed February 18, 2013 05:03PM UTC by samuel6@pdx.edu comment:4

status: pending → new

You can resolve this issue, I believe it's a problem with Chrome, based on reports from Stumbleupon users having the same issue. Thanks.

Changed February 18, 2013 05:06PM UTC by dmethvin comment:5

resolution: → notabug
status: new → closed