179739 2017-11-15 11:16:55 -0800 Consistent handling of out-of-flow children in MathML layout functions 2024-09-25 09:49:15 -0700 1 1 1 Unclassified WebKit MathML WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=123348 InRadar P2 Normal --- 178865 276026 195797 1 fred.wang webkit-unassigned rego webkit-bug-importer oldest_to_newest 1372038 0 fred.wang 2017-11-15 11:16:55 -0800 Extracted from bug 178865. Almost all layout functions in MathML ignore out-of-flow children, except RenderMathMLRow. Consider for example <math> <mtext style="position: absolute; left: 100px; top: 100px;">A</mtext> <mfrac> <mtext style="position: absolute; left: 100px; top: 100px;">B</mtext> <mtext></mtext> </mfrac> </math> where A is absolutely positioned but the numerator B is not. It's not clear whether it's really an important use cases. Maybe we should add special insertPositionedObject calls in all MathML layout functions to be compatible with the CSS behavior. Or maybe we should remove the special handling in RenderMathMLRow to reduce code complexity. 2044661 1 fred.wang 2024-07-04 03:59:15 -0700 MathML Core should now clearly defines how to handle out-of-flow children, so we should follow that: https://w3c.github.io/mathml-core/ Related to that is bug 123348. MathML 3 defines elements with unexpected number of children as "invalid" (e.g. a fraction with three children). MathML Core essentially says that the child count is based on *in-flow* children and that "invalid" markup should be laid out as an mrow. 2050429 2 harpsichen 2024-08-02 17:23:26 -0700 Pull request: https://github.com/WebKit/WebKit/pull/31676 2063046 3 ews-feeder 2024-09-25 09:48:48 -0700 Committed 284225@main (7c0a9d18a4e0): <https://commits.webkit.org/284225@main> Reviewed commits have been landed. Closing PR #31676 and removing active labels. 2063047 4 webkit-bug-importer 2024-09-25 09:49:15 -0700 <rdar://problem/136683070>