Closed
Bug 597540
Opened 15 years ago
Closed 14 years ago
Dotted borders are slow in painting/scrolling
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | final+ |
People
(Reporter: martijn.martijn, Unassigned)
References
()
Details
(Keywords: perf, testcase)
Attachments
(1 file)
588 bytes,
text/html
|
Details |
Scrolling with 1px dotted borders is slow and it seems to be getting slower with more recent builds.
See testcase, when pressing the button, the scrolltest starts.
Some numbers I get:
Seamonkey 1.9.1 build from 2010-07-01: 14217ms
Firefox 3.6.8: 35756ms
Minefield from 2010-09-16: 88801ms (this is with d2d enabled)
This is on Windows 7.
![]() |
||
Updated•15 years ago
|
blocking2.0: --- → ?
We should fix the regression for final. It's probably a D2D bug. (Can you confirm that performance is better with D2D disabled? If so, move it to Graphics.)
blocking2.0: ? → final+
Reporter | ||
Comment 2•14 years ago
|
||
I don't know (anymore?) to turn off D2D. I've set mozilla.widget.render-mode to 0 and layers.accelerate-all to false and then I restarted, but in about:support Direct2D Enabled is still described as true.
Btw, about:support is the url where I was seeing the performance issue.
URL: about:support
Comment 3•14 years ago
|
||
The pref is now called gfx.direct2d.disabled
Comment 4•14 years ago
|
||
Martijn, can you direct me to that scrolling test bookmarklet of yours?
Comment 5•14 years ago
|
||
Is it the one in bug 588402 comment 19?
Comment 6•14 years ago
|
||
(In reply to comment #5)
> Is it the one in bug 588402 comment 19?
I think so! Thanks.
Yep, changing dotted to solid using firebug brings scrolling to normal responsiveness. I'm on D2D+D3D10 Layers, so depends on Bug 588271?
Comment 9•14 years ago
|
||
Bug 588271 will fix this for D2D. Note these dotted borders are also very slow on GDI though, I'm not sure if that will be fixed.
I'm calling this fixed by 588271.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•