RESOLVED FIXED Bug 120953
Remove unnecessary sibling text renderers after attach
https://bugs.webkit.org/show_bug.cgi?id=120953
Summary Remove unnecessary sibling text renderers after attach
Antti Koivisto
Reported 2013-09-07 08:27:12 PDT
The current createTextRenderersForSiblingsAfterAttachIfNeeded code only adds text renderers, never removes them. Style changes can however go either way.
Attachments
patch (46.80 KB, patch)
2013-09-07 08:45 PDT, Antti Koivisto
no flags
fix a few bad test result updates (45.89 KB, patch)
2013-09-07 08:54 PDT, Antti Koivisto
andersca: review+
Antti Koivisto
Comment 1 2013-09-07 08:45:26 PDT
Antti Koivisto
Comment 2 2013-09-07 08:54:38 PDT
Created attachment 210906 [details] fix a few bad test result updates
Anders Carlsson
Comment 3 2013-09-07 10:58:45 PDT
Comment on attachment 210906 [details] fix a few bad test result updates View in context: https://bugs.webkit.org/attachment.cgi?id=210906&action=review > Source/WebCore/ChangeLog:8 > + The current createTextRenderersForSiblingsAfterAttachIfNeeded code only adds text renderers, never removes them. Style changes can go either way. Extra space before "go". > Source/WebCore/style/StyleResolveTree.cpp:305 > + bool hadRenderer = !!whitespaceTextSibling.renderer(); Do you really need the !! here? > LayoutTests/editing/selection/focus-crash-expected.txt:1 > -To run this test manually, click the "Crash me" button. > +To run this test manually, click the "Crash me" button. What's with this test? Looks like it adds whitespace? > LayoutTests/userscripts/user-script-all-frames-expected.txt:1 > +If any thingers appear on this page, the test has failed. Same here. > LayoutTests/userscripts/user-script-top-frame-only-expected.txt:1 > +Two thingers should appear on this page. Otherwise the test has failed. And here!
Antti Koivisto
Comment 4 2013-09-07 11:01:23 PDT
(In reply to comment #3) > What's with this test? Looks like it adds whitespace? Yeah. The new code is also less buggy to other direction. It found a few places where logic dictates we actually need a renderer but failed to create one before.
Antti Koivisto
Comment 5 2013-09-07 11:26:43 PDT
Note You need to log in before you can comment on or make changes to this bug.