Open Bug 511739 Opened 15 years ago Updated 2 years ago

box-shadow is too slow on integrated graphics

Categories

(Core :: Web Painting, defect)

defect

Tracking

()

UNCONFIRMED

People

(Reporter: kroc, Unassigned)

References

()

Details

(Keywords: perf)

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1) Gecko/20090806 Namoroka/3.6a1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1) Gecko/20090806 Namoroka/3.6a1

Just a single box-shadow effect can bring Firefox to its knees when on computers with integrated graphics. Please, however it is done, optimise the ever living crud out of box-shadow

Reproducible: Always

Steps to Reproduce:
1. Visit any site with a box-shadow
2. Scroll
3. Profit!
Actual Results:  
Scrolling is painfully slow on any computer without discreet graphics

Expected Results:  
Smooth scrolling

Sorry this is hardly an enlightening bug report. There’s no other way to put this. Please weave your coding magic however it’s done so that designers can move on and make use of CSS3 features in a practical way. Many thanks.
Dupe of bug 469589 or similar?
Component: General → Layout: View Rendering
Keywords: perf
OS: Mac OS X → All
Product: Firefox → Core
QA Contact: general → layout.view-rendering
Hardware: x86 → All
Version: unspecified → Trunk
That bug specifies one particular potential fix, this bug is more of a meta bug to say that it should be speeded up, by whatever means. If the bugs can be merged, then by all means. :)
I am just adding that Google Chrome 4 (Dev Channel) is blazing fast with multiple shadows, where as Firefox chugs on the same pages. Perhaps use their code as a reference implementation?
Depends on: 509052
Is box shadow fast for you on non-integrated graphics? I wouldn't expect so as I think it's all done on the CPU either way.

If this is just a general "speed up box shadow" bug then I think we already have one of those.
Component: Layout: View Rendering → Layout: Web Painting
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.