WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
70789
Optimize canvas fills / drawImage when covering entire canvas
https://bugs.webkit.org/show_bug.cgi?id=70789
Summary
Optimize canvas fills / drawImage when covering entire canvas
Ben Wells
Reported
2011-10-24 17:48:54 PDT
When compositing fills / drawImage calls in canvas, and the composite mode is Source-In, Source-Out, Destination-In, Destination-Atop or Copy, the canvas is cleared. For all of these modes apart from Copy a temporary buffer is also used. If the fill / drawImage is covering the entire canvas we can optimise away the clear and the use of a temporary buffer.
Attachments
Patch
(4.39 KB, patch)
2011-11-02 19:35 PDT
,
Ben Wells
no flags
Details
Formatted Diff
Diff
Patch using FloatQuad
(4.34 KB, patch)
2011-11-03 16:26 PDT
,
Ben Wells
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Ben Wells
Comment 1
2011-11-02 19:35:36 PDT
Created
attachment 113422
[details]
Patch
Ben Wells
Comment 2
2011-11-02 21:59:27 PDT
It would be nice to do the same optimization for filling a path, but there doesn't seem to be any easy way to see if a path contains a rectangle.
Stephen White
Comment 3
2011-11-03 08:29:35 PDT
Comment on
attachment 113422
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=113422&action=review
Looks good. Thanks for implementing this! r=me
> Source/WebCore/html/canvas/CanvasRenderingContext2D.cpp:1566 > + Path transformedPath; > + transformedPath.addRect(rect); > + transformedPath.transform(state().m_transform); > + > + IntRect canvasRect(0, 0, canvas()->width(), canvas()->height()); > + return transformedPath.contains(canvasRect.minXMinYCorner()) && transformedPath.contains(canvasRect.minXMaxYCorner()) > + && transformedPath.contains(canvasRect.maxXMinYCorner()) && transformedPath.contains(canvasRect.maxXMaxYCorner());
This looks fine, but I'm wondering if it would be easier to use FloatQuad: FloatQuad quad(rect); FloatQuad canvasQuad(FloatRect(0, 0, canvas->width(), canvas->height())); return state().m_transform.mapQuad(quad).containsQuad(canvasQuad); OTOH, I've never actually tried it, so feel free to go with what you've already got.
Ben Wells
Comment 4
2011-11-03 16:26:59 PDT
Created
attachment 113571
[details]
Patch using FloatQuad
Ben Wells
Comment 5
2011-11-03 16:38:41 PDT
Comment on
attachment 113571
[details]
Patch using FloatQuad Using FloatQuad is much nicer. Thanks for the tip!
Stephen White
Comment 6
2011-11-03 18:24:01 PDT
Comment on
attachment 113571
[details]
Patch using FloatQuad Looks great. r=me
WebKit Review Bot
Comment 7
2011-11-03 18:55:45 PDT
Comment on
attachment 113571
[details]
Patch using FloatQuad Clearing flags on attachment: 113571 Committed
r99257
: <
http://trac.webkit.org/changeset/99257
>
WebKit Review Bot
Comment 8
2011-11-03 18:55:50 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug