Bug 221976

Summary: RenderElement::containingBlockForAbsolutePosition may call RenderObject::containingBlock recursively
Product: WebKit Reporter: alan <zalan>
Component: Layout and RenderingAssignee: alan <zalan>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, changseok, esprehn+autocc, ews-watchlist, glenn, kondapallykalyan, pdr, simon.fraser, zalan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

alan
Reported 2021-02-16 10:55:09 PST
when the RenderInline is absolute positioned (which should not happen normally as we blockify out of flow boxes)
Attachments
Patch (3.29 KB, patch)
2021-02-16 11:11 PST, alan 		no flags
DetailsFormatted DiffDiff
Patch (3.34 KB, patch)
2021-02-16 13:43 PST, alan 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
alan
Comment 1 2021-02-16 10:55:38 PST
<rdar://problem/72775667>
alan
Comment 2 2021-02-16 11:11:47 PST
Created attachment 420500 [details] Patch
Simon Fraser (smfr)
Comment 3 2021-02-16 11:15:31 PST
Comment on attachment 420500 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=420500&action=review > Source/WebCore/ChangeLog:9 > + When a RenderInline (incorrectly) happens to be absolute positioned, containingBlockForAbsolutePosition() calls containingBlock() Do we know why this happens? Should we assert when it does?
alan
Comment 4 2021-02-16 13:43:34 PST
Created attachment 420534 [details] Patch
EWS
Comment 5 2021-02-16 14:55:58 PST
Committed r272931: <https://commits.webkit.org/r272931> All reviewed patches have been landed. Closing bug and clearing flags on attachment 420534 [details].
Note You need to log in before you can comment on or make changes to this bug.