and move some code from FloatingContext to FloatAvoider
Created attachment 348239 [details] Patch
Comment on attachment 348239 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=348239&action=review > Source/WebCore/layout/floats/FloatAvoider.h:64 > + void resetHorizontalConstraint(); Some of these are singulars like here "Constraint". > Source/WebCore/layout/floats/FloatingContext.cpp:71 > + FloatAvoider::HorizontalConstraints horizontalConstraints() const; And some are plural. Is there some logic to this?
Comment on attachment 348239 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=348239&action=review > Source/WebCore/layout/floats/FloatingContext.cpp:228 > + floatAvoider.setHorizontalConstraints(floats.horizontalConstraints()); > + floatAvoider.setVerticalConstraint(floats.verticalPosition()); It looks strange that the second one is reading floats.verticalPosition instead of floats.verticalConstraint. But maybe it makes sense?
Committed r235423: <https://trac.webkit.org/changeset/235423>
<rdar://problem/43797393>
(In reply to Antti Koivisto from comment #2) > Comment on attachment 348239 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=348239&action=review > > > Source/WebCore/layout/floats/FloatAvoider.h:64 > > + void resetHorizontalConstraint(); > > Some of these are singulars like here "Constraint". > > > Source/WebCore/layout/floats/FloatingContext.cpp:71 > > + FloatAvoider::HorizontalConstraints horizontalConstraints() const; > > And some are plural. Is there some logic to this? Fixed. No logic, oversight.
<rdar://problem/43797406>
(In reply to Antti Koivisto from comment #3) > Comment on attachment 348239 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=348239&action=review > > > Source/WebCore/layout/floats/FloatingContext.cpp:228 > > + floatAvoider.setHorizontalConstraints(floats.horizontalConstraints()); > > + floatAvoider.setVerticalConstraint(floats.verticalPosition()); > > It looks strange that the second one is reading floats.verticalPosition > instead of floats.verticalConstraint. But maybe it makes sense? Fixed.
<rdar://problem/43797410>