WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
194198
Make setNeedsLayout on the root more explicitly about triggering its side-effects
https://bugs.webkit.org/show_bug.cgi?id=194198
Summary
Make setNeedsLayout on the root more explicitly about triggering its side-eff...
Simon Fraser (smfr)
Reported
2019-02-02 17:20:57 PST
Make setNeedsLayout on the root more explicitly about triggering its side-effects
Attachments
Patch
(25.52 KB, patch)
2019-02-02 17:32 PST
,
Simon Fraser (smfr)
no flags
Details
Formatted Diff
Diff
Patch
(25.77 KB, patch)
2019-02-02 17:45 PST
,
Simon Fraser (smfr)
no flags
Details
Formatted Diff
Diff
Archive of layout-test-results from ews106 for mac-highsierra-wk2
(2.51 MB, application/zip)
2019-02-02 19:06 PST
,
EWS Watchlist
no flags
Details
Patch
(25.93 KB, patch)
2019-02-02 20:34 PST
,
Simon Fraser (smfr)
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1
2019-02-02 17:32:04 PST
Comment hidden (obsolete)
Created
attachment 360988
[details]
Patch
Simon Fraser (smfr)
Comment 2
2019-02-02 17:45:26 PST
Comment hidden (obsolete)
Created
attachment 360989
[details]
Patch
EWS Watchlist
Comment 3
2019-02-02 19:06:55 PST
Comment hidden (obsolete)
Comment on
attachment 360989
[details]
Patch
Attachment 360989
[details]
did not pass mac-wk2-ews (mac-wk2): Output:
https://webkit-queues.webkit.org/results/11011001
New failing tests: tiled-drawing/header-and-footer-hit-testing-in-frame.html
EWS Watchlist
Comment 4
2019-02-02 19:06:56 PST
Comment hidden (obsolete)
Created
attachment 360991
[details]
Archive of layout-test-results from ews106 for mac-highsierra-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews106 Port: mac-highsierra-wk2 Platform: Mac OS X 10.13.6
Simon Fraser (smfr)
Comment 5
2019-02-02 20:34:30 PST
Created
attachment 360995
[details]
Patch
Antti Koivisto
Comment 6
2019-02-03 10:08:06 PST
Comment on
attachment 360995
[details]
Patch r=me
WebKit Commit Bot
Comment 7
2019-02-03 17:48:19 PST
Comment on
attachment 360995
[details]
Patch Clearing flags on attachment: 360995 Committed
r240912
: <
https://trac.webkit.org/changeset/240912
>
WebKit Commit Bot
Comment 8
2019-02-03 17:48:21 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 9
2019-02-03 17:49:30 PST
<
rdar://problem/47776051
>
Michael Catanzaro
Comment 10
2019-02-04 07:48:48 PST
Committed
r240923
: <
https://trac.webkit.org/changeset/240923
>
zalan
Comment 11
2019-02-04 08:07:16 PST
Comment on
attachment 360995
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=360995&action=review
> Source/WebCore/ChangeLog:8 > + Calling setNeedsLayout() on the FrameView or RenderView is an odd concept; the render tree
I think calling setNeedsLayout on the RenderView is an ok concept. It just means that the ICB got resized and now it needs to propagate this new size to its descendants (like stretchy html/body in quirks mode, or just width in general).
> Source/WebCore/page/FrameView.cpp:2928 > + RenderView* renderView = this->renderView(); > + if (renderView->usesCompositing()) { > + if (auto* rootLayer = renderView->layer()) > + renderView->layer()->setNeedsCompositingConfigurationUpdate();
I'd prefer early returns here: { auto* renderView = this->renderView(); if (!renderView->usesCompositing()) return; auto* rootLayer = renderView->layer() if (!rootLayer) return; rootLayer->setNeedsCompositingConfigurationUpdate(); } or just fix: if (auto* rootLayer = renderView->layer()) renderView->layer()->setNeedsCompositingConfigurationUpdate(); -> rootLayer->setNeedsCompositingConfigurationUpdate();
> Source/WebCore/page/FrameView.cpp:2938 > + RenderView* renderView = this->renderView(); > + if (renderView->usesCompositing()) { > + if (auto* rootLayer = renderView->layer()) > + renderView->layer()->setNeedsCompositingGeometryUpdate(); > + }
same as above
> Source/WebCore/page/FrameViewLayoutContext.cpp:326 > renderView->setNeedsLayout(); > + scheduleLayout();
It's odd that the RenderView is the only renderer in the tree that does not schedule layout. I think this should be fixed in setNeedsLayout.
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