Flicker when scrolling position:fixed box passes over frame with view (overflow:auto)

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
11 years ago
4 months ago

People

(Reporter: ryme.peyrard, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: DUPEME, URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9) Gecko/2008052906 Firefox/3.0

Good morning
there seems to be a problem with the overflow causing a lag in the display pages
[url]http://koogar.alorys-hebergement.com/kwsphp/index.php?mod=forum&ac=voir&id=6494&debut=0&cat=40[/url]
[url]http://koogar.alorys-hebergement.com/kwsphp/index.php?mod=forum&ac=voir&cat=41&id=6534&debut=0#post58210[/url]


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Component: General → Layout: View Rendering
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → layout.view-rendering
Hardware: PC → All
Summary: overflow → Flicker when scrolling position:fixed box passes over frame with view (overflow:auto)
Whiteboard: DUPEME

Comment 1

9 years ago
Steps to reproduce:

1. Go to a site with a [position: fixed] element eg. navigation on the left hand side of the QuirksBlog [http://www.quirksmode.org/blog/index.html]

2. Scroll downwards, look closely at the rendering of text in the main column as it passes through the vertical space occupied by the fixed element

3. You'll see a scanline-like horizontal line that indicate a lag in rendering of the text elements as they moves upwards when the page is scrolled

4. Using Firebug, change the overflow property to something, say hidden, and the problem disappears

Also notice the stuttering movement of the navigation elements as you start scrolling from the top. Is this a lag in Javascript?
Is this still happening?
(Assignee)

Updated

4 months ago
Component: Layout: View Rendering → Layout: Web Painting
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.