[Webkit-unassigned] [Bug 179682] Incorrect bounds inside <mover>/<munder> when a stretchy operator is present

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=179682

--- Comment #51 from Frédéric Wang (:fredw) <fred.wang at free.fr> ---
(In reply to Minsheng Liu from comment #50)
> When layoutIfNeeded() is called on <msub>, it will find its immediate child
> <mover> clean, so the recursion will not go down. I have tested and making
> sure the whole chain from the immediate child to the operator at its core
> dirty is crucial for correct layout.
> 
> Note that this approach only requires minimal re-layout. Essentially, only
> logicalWidth() and location() are updated. Therefore, I could get rid of my
> initially complicated first loop and counter-based lock and all other crazy
> stuff. I think we are optimal here.

Sorry, I was not clear. I mean (quickly looking to the implementation of layoutIfNeeded) it seems marking the <mo> at the core dirty will also already mark the whole ancestor chain and then you just need to layout the direct child.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171204/1965f729/attachment.html>