WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
61891
Switch paintReplaced to use IntPoint
https://bugs.webkit.org/show_bug.cgi?id=61891
Summary
Switch paintReplaced to use IntPoint
Levi Weintraub
Reported
2011-06-01 16:22:43 PDT
Ongoing tx/ty removal.
Attachments
Patch
(11.85 KB, patch)
2011-06-01 18:24 PDT
,
Levi Weintraub
no flags
Details
Formatted Diff
Diff
Patch
(35.49 KB, patch)
2011-06-02 13:40 PDT
,
Levi Weintraub
no flags
Details
Formatted Diff
Diff
Patch
(36.19 KB, patch)
2011-06-02 14:02 PDT
,
Levi Weintraub
no flags
Details
Formatted Diff
Diff
Patch for landing
(36.93 KB, patch)
2011-06-02 14:20 PDT
,
Levi Weintraub
no flags
Details
Formatted Diff
Diff
Show Obsolete
(3)
View All
Add attachment
proposed patch, testcase, etc.
Levi Weintraub
Comment 1
2011-06-01 18:24:37 PDT
Created
attachment 95696
[details]
Patch
Eric Seidel (no email)
Comment 2
2011-06-01 22:55:15 PDT
Comment on
attachment 95696
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=95696&action=review
> Source/WebCore/rendering/RenderHTMLCanvas.cpp:60 > + rect.move(paintOffset);
So does this move to the point, or treat the point as a size? I think IntRect::move(IntPoint) is confusing and should probably be removed. Since I believe this does not move to the point, but rahter by the size of the point, I think rect.move(toSize(paintOffset)) might end up clearer. This again is the tx/ty being used for different things in different places coming to bite us.
> Source/WebCore/rendering/RenderImage.cpp:254 > + IntSize imageOffset;
Why is this way out here if it's only used in that one place?
Simon Fraser (smfr)
Comment 3
2011-06-02 08:04:11 PDT
Maybe IntRect::moveBy(const IntPoint&)?
Levi Weintraub
Comment 4
2011-06-02 11:21:53 PDT
Comment on
attachment 95696
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=95696&action=review
>> Source/WebCore/rendering/RenderHTMLCanvas.cpp:60 >> + rect.move(paintOffset); > > So does this move to the point, or treat the point as a size? I think IntRect::move(IntPoint) is confusing and should probably be removed. Since I believe this does not move to the point, but rahter by the size of the point, I think rect.move(toSize(paintOffset)) might end up clearer. This again is the tx/ty being used for different things in different places coming to bite us.
I like "moveBy" and that doesn't introduce an unnecessary copy. How does that sound to you, Eric?
>> Source/WebCore/rendering/RenderImage.cpp:254 >> + IntSize imageOffset; > > Why is this way out here if it's only used in that one place?
It's used in two places is why -- see L289 :)
Eric Seidel (no email)
Comment 5
2011-06-02 11:23:28 PDT
Sounds fine.
Levi Weintraub
Comment 6
2011-06-02 11:33:04 PDT
Comment on
attachment 95696
[details]
Patch Cool. Clearing the flag pending that change.
Levi Weintraub
Comment 7
2011-06-02 13:40:41 PDT
Created
attachment 95801
[details]
Patch
WebKit Review Bot
Comment 8
2011-06-02 13:57:17 PDT
Comment on
attachment 95801
[details]
Patch
Attachment 95801
[details]
did not pass chromium-ews (chromium-xvfb): Output:
http://queues.webkit.org/results/8754855
Eric Seidel (no email)
Comment 9
2011-06-02 14:01:28 PDT
Comment on
attachment 95801
[details]
Patch Looks reasonable to me. What's up with the cr bot?
Levi Weintraub
Comment 10
2011-06-02 14:02:33 PDT
Created
attachment 95802
[details]
Patch
Eric Seidel (no email)
Comment 11
2011-06-02 14:09:09 PDT
Comment on
attachment 95802
[details]
Patch OK.
Levi Weintraub
Comment 12
2011-06-02 14:09:47 PDT
(In reply to
comment #11
)
> (From update of
attachment 95802
[details]
) > OK.
Thanks! I'd missed a file not used in the Mac build. I'll wait for EWS to verify then land.
Levi Weintraub
Comment 13
2011-06-02 14:20:50 PDT
Created
attachment 95809
[details]
Patch for landing
WebKit Commit Bot
Comment 14
2011-06-02 19:42:42 PDT
Comment on
attachment 95809
[details]
Patch for landing Rejecting
attachment 95809
[details]
from commit-queue. Failed to run "['./Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=cr-jail-8', 'land-a..." exit_code: 1 Last 500 characters of output: autoinstalled/mechanize/_urllib2_fork.py", line 332, in _call_chain result = func(*args) File "/mnt/git/webkit-commit-queue/Tools/Scripts/webkitpy/thirdparty/autoinstalled/mechanize/_urllib2_fork.py", line 1170, in https_open return self.do_open(conn_factory, req) File "/mnt/git/webkit-commit-queue/Tools/Scripts/webkitpy/thirdparty/autoinstalled/mechanize/_urllib2_fork.py", line 1118, in do_open raise URLError(err) urllib2.URLError: <urlopen error [Errno 60] Operation timed out> Full output:
http://queues.webkit.org/results/8759402
Eric Seidel (no email)
Comment 15
2011-06-03 07:39:22 PDT
Comment on
attachment 95809
[details]
Patch for landing Clearly we need to catch these timeout exceptions and not fail patches.
WebKit Commit Bot
Comment 16
2011-06-03 07:41:21 PDT
Comment on
attachment 95809
[details]
Patch for landing Rejecting
attachment 95809
[details]
from commit-queue. Failed to run "['./Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=cr-jail-8', 'apply-..." exit_code: 2 Last 500 characters of output: g rejects to file Source/WebCore/rendering/RenderVideo.cpp.rej patching file Source/WebCore/rendering/RenderVideo.h Hunk #1 FAILED at 66. 1 out of 1 hunk FAILED -- saving rejects to file Source/WebCore/rendering/RenderVideo.h.rej patching file Source/WebCore/rendering/RenderView.cpp Hunk #1 FAILED at 273. 1 out of 1 hunk FAILED -- saving rejects to file Source/WebCore/rendering/RenderView.cpp.rej Failed to run "[u'/mnt/git/webkit-commit-queue/Tools/Scripts/svn-apply', u'--force']" exit_code: 1 Full output:
http://queues.webkit.org/results/8764121
Levi Weintraub
Comment 17
2011-06-03 10:58:04 PDT
Comment on
attachment 95809
[details]
Patch for landing Clearing flags
Levi Weintraub
Comment 18
2011-06-03 10:59:47 PDT
Landed in
r87989
. Eric, Adam: The timed-out commit queue actually landed this patch but didn't make note of it!
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