Closed Bug 308222 Opened 19 years ago Closed 17 years ago

overflow:auto on div after adjusting margin-left problem

Categories

(Core :: Web Painting, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: mkmelin, Assigned: roc)

Details

(Keywords: regression, testcase)

Attachments

(3 files)

In the testcase I'm about to attach, a wide div containing other divs are
scrolled  so that only one of the innner divs are visible at the time. 

When the innner div has overflow:auto - and the div is scrolled back - parts of
the div next to it is left visible. Also, the right margin of the inner div does
not display until you drag the mouse over it. So basically, things are left
partly  visible outside the margin of the div. 

This works fine in firefox 1.0.x, opera8, ie. Problems in recent nightlies, and
at least back to 2005-03-01, I didn't have any older build to test with. Both
win and linux.
Attached file testcase
Click the button in this testcase twice. Notice stuff are kind of left behind.
Reproducible with Mozilla 1.8a5 but WFM with Mozilla 1.8a4.
About the testcase: When switching to another tab or minimizing the window
you'll notice that the garbage goes away. 
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
It would be helpful if you could reduce this testcase to the bare minimum
required to show the bug.
Attached file testcase2
This is a minimal testcase that shows the bug.
Attached patch fixSplinter Review
This fixes the bug, but I'm a bit concerned about the potential impact. I don't
immediately see a better way though.
In particular I'm concerned that hiding and showing child windows might be slow
or have some other impact (e.g., affect focus).
Any chance this fix will get checked in? Slow would be better than all wrong...
if it's not extremely slow.

In the testcase: the garbage isn't left behind with overflow:visible either btw.
overflow:auto and overflow:scroll get's it wrong.
This is probably too risky for branch at this point. For trunk this problem will
go away with some other work.
Flags: blocking1.9a1?
Flags: blocking1.9a1? → blocking1.9-
Whiteboard: [wanted-1.9]
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
On trunk there's some flickery stuff on Windows but it's very transitory, you always end up with the right rendering. I hope that will go away with Compositor. We certainly aren't going to fix this on the 1.8 branch. Since this is labelled a branch bug, I probably should call it WONTFIX, but it makes more sense to point this at trunk and mark it FIXED.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Version: 1.8 Branch → Trunk
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: