Closed Bug 172626 Opened 22 years ago Closed 22 years ago

Very slow scrolling unless the background is commented out

Categories

(Core :: Layout, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 90198

People

(Reporter: jesup, Assigned: roc)

References

()

Details

(Keywords: perf)

When viewing Hixie's weblog, scrolling is VERY slow.  Tried it on a BSD machine
(P3-800) and an extremely fast dual-cpu (2 x 2.0GHz P4 Xeon) Linux machine. 
Hixie says he doesn't see this on Windows.

I did a save page (complete) of Hixie's weblog, and loaded it into a tab.  Note
that not everything gets saved, which is another bug.  The page still scrolls
slowly.

Even using the debug stylesheet for the page, which disables the background in
debug.css with 

* {   background: transparent ! important; }

it's still slow.  Commenting out

html { background: url(../images/astrophy/original) 100% 99% fixed no-repeat; }

from spaced.css makes it fast, regardless of whether debug.css is loaded. 
Interestingly, adding a <base href="http://ln.hixie.ch/"> to the <head> _also_
makes scrolling fast - though when loaded entirely from the original URL it's
slow.  Very very weird.

(there was a discussion between myself, Hixie and Roc on IRC).
QA -> Ian
Keywords: perf
QA Contact: petersen → ian
looks like a duplicate of bug 90198 to me
The following 4 bugs seem to be related (or duplicates):

bug 90198  - scrolling very slow (fixed background)
bug 172626 - Very slow scrolling unless the background is commented out
bug 176150 - Fixed backgrounds cause horribly slow scrolling
bug 184556 - style rule for fixed background causes lag when text scrolled
Surely a dupe, look at this:

"Commenting out

html { background: url(../images/astrophy/original) 100% 99% fixed no-repeat; }

from spaced.css makes it fast, regardless of whether debug.css is loaded. "

And especially at the "fixed".

*** This bug has been marked as a duplicate of 90198 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.