commit | 63360945c80fadd9d104790e566f3dc7e0ac90b4 | [log] [tgz] |
---|---|---|
author | Frédéric Wang <fwang@igalia.com> | Fri Sep 03 09:30:25 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 03 09:30:25 2021 |
tree | 77756c6b4f0f8d13916f0449f4b5c48e3419abc2 | |
parent | bca2778680e36385504bee34829bb183d64b979d [diff] |
[mathml] Embellished operators and stretch properties This is part patch of a series of CL to implement MathML stretchy operators as well as embellished operators [1]. It handles the cases "If there is a block stretch size constraint or an inline stretch size constraint then the element being laid out is an embellished operator" from [2] and [3]. A typical use case is the following, the inner <mover> element is an embellished operator (a over brace with the " k times" as over script). Its core operator should stretch horizontally to cover the inline size of the <mrow> element "x + x + … + x". Without that CL, the horizontal over brace would just cover the size of the " k times" over script. <math> <mover> <mrow> <mi>x</mi> <mo>+</mo> <mi>x</mi> <mo>+</mo> <mo>…</mo> <mo>+</mo> <mi>x</mi> </mrow> <mover> <mo>⏞</mo> <mrow> <mi>k</mi><mtext> times</mtext> </mrow> </mover> </mover> </math> The outer <mover> passes inline stretch constraint to its over script per [3]. Now using the rule from [3] implemented in this CL, the inner <mover> will just use that inline stretch constraint to stretch the over brace. Note, that elements can receive a stretch constraint orthogonal to the direction they normally stretch their children. In the example below, the <munder> is an embellished operator (a left parenthesis with a "1" under script). Although it normally stretches its children horizontally, the parenthesis is stretched vertically using the stretch constraint received from its parent <mrow>. <math> <mrow> <munder> <mo>(</mo> <mn>1</mn> </munder> <munderover> <mn>2</mn> <mn>3</mn> <mn>4</mn> </munderover> </mrow> </math> New tests integrated into this CL cover all possible combinations: - third_party/stretch-along-block-axis-001.html is extended to test case when the <mo> is replaced with an embellished operator with <mrow> or <munderover>. It tests when the mrow and underover algorithms forward any inherited block stretch size constraint to their children. It also tests when the mrow algorithm calculates and passes a block stretch size constraint to embellished operator children. - presentation-markup/scripts/underover-stretchy-00[23].html are copies of underover-stretchy-001 with the <mo> embellished with <mrow> and <munderover> respectively. They respectively test when the mrow and underover algorithms forward any inherited inline stretch size constraint to their children. They also test when the munderover algorithm calculates and passes an inline stretch size constraint to embellished operator children. [1] https://w3c.github.io/mathml-core/#embellished-operators [2] https://w3c.github.io/mathml-core/#algorithm-for-stretching-operators-along-the-block-axis [3] https://w3c.github.io/mathml-core/#algorithm-for-stretching-operators-along-the-inline-axis Bug: 6606, 1124298, 1124301 Change-Id: I682e5343c1440e657b10933e1bfe7fdf63d9e112 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3121110 Commit-Queue: Frédéric Wang <fwang@igalia.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#918027}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.