[Webkit-unassigned] [Bug 179682] Incorrect bounds inside <mover>/<munder> when a stretchy operator is present
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Nov 27 17:57:00 PST 2017
https://bugs.webkit.org/show_bug.cgi?id=179682
Minsheng Liu <lambda at liu.ms> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #327719| |review-, commit-queue-
Flags| |
--- Comment #18 from Minsheng Liu <lambda at liu.ms> ---
Created attachment 327719
--> https://bugs.webkit.org/attachment.cgi?id=327719&action=review
the algorithm in action (just for visual comparison, not a patch to review)
I add a helper variable to RenderMathMLOperator to lock the stretch width of those operators. The motivation should hopefully be lucid: after stretching the operator and re-layout its ancestors, the recursive call will automatically revert the stretched width, an undesired behavior.
The other trick is that I set stretchWidth to base()’s width in the second loop. It is a bit tricky (I am not sure if such code is welcome here for WebKit) but it reduces code reduplication.
--
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/20171128/a1e3274a/attachment.html>
More information about the webkit-unassigned
mailing list