WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
79724
Stop doubling maximalOutlineSize during painting
https://bugs.webkit.org/show_bug.cgi?id=79724
Summary
Stop doubling maximalOutlineSize during painting
Julien Chaffraix
Reported
2012-02-27 17:32:40 PST
Several call sites are wrongly doubling the maximal outline when manipulating the repaint rectangle: * RenderReplaced * RenderTableSection * RenderTableCell There is no historical explanation for the doubling. Moreover the rest of the code handle the maximalOutlineSize by just inflating the repaint rectangle once so it looks like a bug!
Attachments
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic.
(4.79 KB, patch)
2012-02-28 11:55 PST
,
Julien Chaffraix
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Julien Chaffraix
Comment 1
2012-02-28 11:55:43 PST
Created
attachment 129303
[details]
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic.
Tony Chang
Comment 2
2012-02-29 10:27:07 PST
Comment on
attachment 129303
[details]
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic. View in context:
https://bugs.webkit.org/attachment.cgi?id=129303&action=review
> Source/WebCore/ChangeLog:8 > + Refactoring only, covered by existing tests (mostly repaint ones).
Can you name the pixel tests that need a rebaseline from this? Maybe we can pre-emptively mark them in test_expectations.txt so the bots don't go red.
Julien Chaffraix
Comment 3
2012-02-29 10:32:47 PST
Comment on
attachment 129303
[details]
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic. View in context:
https://bugs.webkit.org/attachment.cgi?id=129303&action=review
>> Source/WebCore/ChangeLog:8 >> + Refactoring only, covered by existing tests (mostly repaint ones). > > Can you name the pixel tests that need a rebaseline from this? Maybe we can pre-emptively mark them in test_expectations.txt so the bots don't go red.
There is none that needs to be rebaselined. However there are several tests involving tables and replaced elements in our tree. The repaint tests are the one that checks that I did not break our repainting by "shrinking" the outline. I can change the wording if you want.
Tony Chang
Comment 4
2012-02-29 11:04:53 PST
Comment on
attachment 129303
[details]
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic. View in context:
https://bugs.webkit.org/attachment.cgi?id=129303&action=review
>>> Source/WebCore/ChangeLog:8 >>> + Refactoring only, covered by existing tests (mostly repaint ones). >> >> Can you name the pixel tests that need a rebaseline from this? Maybe we can pre-emptively mark them in test_expectations.txt so the bots don't go red. > > There is none that needs to be rebaselined. However there are several tests involving tables and replaced elements in our tree. The repaint tests are the one that checks that I did not break our repainting by "shrinking" the outline. I can change the wording if you want.
I see, I was confused by "Stop doubling maximalOutlineSize during painting", which sounds like a different behavior. I think the current working is OK. Feel free to cq+.
Julien Chaffraix
Comment 5
2012-02-29 11:32:08 PST
Comment on
attachment 129303
[details]
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic. View in context:
https://bugs.webkit.org/attachment.cgi?id=129303&action=review
>>>> Source/WebCore/ChangeLog:8 >>>> + Refactoring only, covered by existing tests (mostly repaint ones). >>> >>> Can you name the pixel tests that need a rebaseline from this? Maybe we can pre-emptively mark them in test_expectations.txt so the bots don't go red. >> >> There is none that needs to be rebaselined. However there are several tests involving tables and replaced elements in our tree. The repaint tests are the one that checks that I did not break our repainting by "shrinking" the outline. I can change the wording if you want. > > I see, I was confused by "Stop doubling maximalOutlineSize during painting", which sounds like a different behavior. I think the current working is OK. Feel free to cq+.
OK , cqinating :-)
WebKit Review Bot
Comment 6
2012-02-29 12:50:00 PST
Comment on
attachment 129303
[details]
Proposed refactoring: remove the doubling and introduce some localRepaintRect to simplify the logic. Clearing flags on attachment: 129303 Committed
r109246
: <
http://trac.webkit.org/changeset/109246
>
WebKit Review Bot
Comment 7
2012-02-29 12:50:06 PST
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