-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vertical stretchy rule: Define what happens when maxsize < minsize #109
Comments
FYI: MathPlayer handled this by setting minsize to maxsize (i.e, it basically choose maxsize). |
From Monday meeting: check similar behavior in CSS. |
CSS always respects the minsize, so we should do the same (i.e. maxsize set to minsize) for MathML |
Consensus from 2019/11/11: keep as it i.e. do like CSS (minsize wins over maxsize) |
w3c/mathml#109 Not closing as this likely still need tests.
This has "needs polyfill" label, but I don't see why, so I'm removing it. In fact, I think only the 'needs tests' label is all that should remain. @fred-wang: can you verify and update the labels if this is true. |
@NSoiffer I think the original idea was to put all the labels when an issue is opened and then let people check and remove them. But in that case, I agree that's no longer needed. |
I'm removing the 'needs resolution' since we have a resolution. |
* Add MathML test for edge cases of minsize and maxsize w3c/mathml#109 * fix title
…e and maxsize, a=testonly Automatic update from web-platform-tests Add MathML test for edge cases of minsize and maxsize (#23743) * Add MathML test for edge cases of minsize and maxsize w3c/mathml#109 * fix title -- wpt-commits: d7ba3d542968b63ddba6f809c5bbeba3d99cf2cb wpt-pr: 23743
…e and maxsize, a=testonly Automatic update from web-platform-tests Add MathML test for edge cases of minsize and maxsize (#23743) * Add MathML test for edge cases of minsize and maxsize w3c/mathml#109 * fix title -- wpt-commits: d7ba3d542968b63ddba6f809c5bbeba3d99cf2cb wpt-pr: 23743
I think this is what Bruce actually wanted to mention this during one the mstyle@minsize discussion.
If maxsize < minsize then one can only satisfy one of the constraint. In Gecko it was implemented so that the minsize is satisfied. As a consequence, I implemented the same in WebKit.
However, maybe maxsize < minsize should just be treated as an invalid request and hence ignored?
The text was updated successfully, but these errors were encountered: