RESOLVED FIXED 183187
Remove RenderElement::s_affectsParentBlock
https://bugs.webkit.org/show_bug.cgi?id=183187
Summary Remove RenderElement::s_affectsParentBlock
zalan
Reported 2018-02-27 15:24:46 PST
This is a hack to track state change between styleWillChange and styleDidChange.
Attachments
Patch (3.71 KB, patch)
2018-02-27 16:19 PST, zalan
no flags
Patch (3.84 KB, patch)
2018-02-27 19:22 PST, zalan
no flags
Patch (4.06 KB, patch)
2018-02-28 07:56 PST, zalan
no flags
Radar WebKit Bug Importer
Comment 1 2018-02-27 16:14:09 PST
zalan
Comment 2 2018-02-27 16:19:46 PST
zalan
Comment 3 2018-02-27 19:22:10 PST
Frédéric Wang (:fredw)
Comment 4 2018-02-28 07:15:55 PST
Comment on attachment 334724 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=334724&action=review > Source/WebCore/rendering/RenderElement.cpp:-97 > -bool RenderElement::s_affectsParentBlock = false; Any reason why you do the removal of s_noLongerAffectsParentBlock in the separate bug 183196? Or it's just to be careful and do smaller changes? > Source/WebCore/rendering/RenderElement.cpp:-773 > - s_affectsParentBlock = false; Normally you should remove braces per https://webkit.org/code-style-guidelines/#braces-one-line although I understand this else will eventually go away. > Source/WebCore/rendering/RenderElement.cpp:812 > + && parent() && (parent()->isRenderBlockFlow() || parent()->isRenderInline())) { I wonder whether keeping a local affectsParentBlock variable would help making the meaning of this big conditional more explicit or whether the comment is enough.
Antti Koivisto
Comment 5 2018-02-28 07:19:23 PST
r=me
zalan
Comment 6 2018-02-28 07:30:35 PST
(In reply to Frédéric Wang (:fredw) from comment #4) > Comment on attachment 334724 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=334724&action=review > > > Source/WebCore/rendering/RenderElement.cpp:-97 > > -bool RenderElement::s_affectsParentBlock = false; > > Any reason why you do the removal of s_noLongerAffectsParentBlock in the > separate bug 183196? Or it's just to be careful and do smaller changes? > just being careful (moving the s_noLongerAffectsParentBlock needs a bit more work since it has a bit of a dependency) > > Source/WebCore/rendering/RenderElement.cpp:-773 > > - s_affectsParentBlock = false; > > Normally you should remove braces per > https://webkit.org/code-style-guidelines/#braces-one-line although I > understand this else will eventually go away. Yeah, I'll remove the braces anyway. > > > Source/WebCore/rendering/RenderElement.cpp:812 > > + && parent() && (parent()->isRenderBlockFlow() || parent()->isRenderInline())) { > > I wonder whether keeping a local affectsParentBlock variable would help > making the meaning of this big conditional more explicit or whether the > comment is enough. I was thinking about that too but for some reason I decided not to. but now I am leaning towards having the variable there.
zalan
Comment 7 2018-02-28 07:53:50 PST
(In reply to zalan from comment #6) > (In reply to Frédéric Wang (:fredw) from comment #4) > > Comment on attachment 334724 [details] > > Patch > > > > View in context: > > https://bugs.webkit.org/attachment.cgi?id=334724&action=review > > > > > Source/WebCore/rendering/RenderElement.cpp:-97 > > > -bool RenderElement::s_affectsParentBlock = false; > > > > Any reason why you do the removal of s_noLongerAffectsParentBlock in the > > separate bug 183196? Or it's just to be careful and do smaller changes? > > > just being careful (moving the s_noLongerAffectsParentBlock needs a bit more > work since it has a bit of a dependency) > > > > Source/WebCore/rendering/RenderElement.cpp:-773 > > > - s_affectsParentBlock = false; > > > > Normally you should remove braces per > > https://webkit.org/code-style-guidelines/#braces-one-line although I > > understand this else will eventually go away. > Yeah, I'll remove the braces anyway. > > > > > > Source/WebCore/rendering/RenderElement.cpp:812 > > > + && parent() && (parent()->isRenderBlockFlow() || parent()->isRenderInline())) { > > > > I wonder whether keeping a local affectsParentBlock variable would help > > making the meaning of this big conditional more explicit or whether the > > comment is enough. > I was thinking about that too but for some reason I decided not to. but now > I am leaning towards having the variable there. Though this is all temporary anyway since the point of this exercise is to move the mutation logic to the tree updater.
zalan
Comment 8 2018-02-28 07:56:04 PST
WebKit Commit Bot
Comment 9 2018-02-28 08:31:38 PST
Comment on attachment 334744 [details] Patch Clearing flags on attachment: 334744 Committed r229091: <https://trac.webkit.org/changeset/229091>
WebKit Commit Bot
Comment 10 2018-02-28 08:31:39 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.