Closed Bug 221614 Opened 21 years ago Closed 15 years ago

Browser hangup and inproper scrolling using large number of spans inside a div where overflow:auto is enabled

Categories

(Core :: Web Painting, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 215055

People

(Reporter: bmclean, Assigned: roc)

Details

(Whiteboard: closeme 2009-08-01)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

The page will render wrong (or not at all) once scrolled down by at least 20%.
The exact ammount depends on the number of <span> rows. 

Reproducible: Always

Steps to Reproduce:
1. Create file:
<html>
<body>
<div style="overflow:auto">
        <span>This is a test. asdfasdfasdf<br></span>
	<span>This is a test. asdfasdfasdf<br></span>
	<!-- ***** snip, make about 3000 copies of the span line above *****-->
	
</div>
</body>
</html>



2. Open file in Mozilla
3. Drag vertical scroll bar around.

Actual Results:  
The browser will hangup for a while. If you scroll down far enough, the page
will go blank. Scroll back up and the text starts displaying on top of itself.

Expected Results:  
The entire page should scroll correctly.
Nothing to do with CTL (please see the component description).

This is a duplicate of the "widgets on win32 use 16-bit coordinates" bug...
Assignee: prabhat.hegde → roc
Component: Complex Text Layout → Layout: View Rendering
QA Contact: art → ian
Whiteboard: DUPEME
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
Here I am. 
I've found out this anomaly too. It takes place if overflow is set up to *auto* or *scroll*. Basically it seems that if you define a div with overflow set up to *auto* or *scroll* the div doesn't show all the content within, as if it had  a fixed height set up. And it happens regardless of the content (simple text, ul, li).
testing with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Do you still see this problem using Firefox 3.5?  Please update the bug, and close/alter bug if appropriate.
Whiteboard: DUPEME → closeme 2009-08-01
No reply, INCO. Please reopen if you are seeing this in Firefox 3.5.2 or later in Firefox safe mode and a new profile with the latest plugins.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Profiles
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
This certainly isn't INCOMPLETE. This could be fixed by the "remove widgets" landing. Comment 1 mentions this is a duplicate of bug 215055, so let's mark it a duplicate of that bug, but perhaps the reporter could test in current trunk build if the perfmance also has improved in current trunk build.
Resolution: INCOMPLETE → DUPLICATE
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.