-
Notifications
You must be signed in to change notification settings - Fork 20
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
Simplification of the menclose element #105
Comments
Discussion is still open: w3c/mathml#105 so let's only check some minimal <mrow> support. Igalia does not plan to implement this element in Chromium for now so making detection too strict is causing test failures.
Discussion is still open: w3c/mathml#105 so let's only check some minimal <mrow> support. Igalia does not plan to implement this element in Chromium for now so making detection too strict is causing test failures.
…a=testonly Automatic update from web-platform-tests Relax feature-detection for <menclose> (#21256) Discussion is still open: w3c/mathml#105 so let's only check some minimal <mrow> support. Igalia does not plan to implement this element in Chromium for now so making detection too strict is causing test failures. -- wpt-commits: ee2b3c3d8740dcfccf6d6a0c5a371335dd198654 wpt-pr: 21256
…a=testonly Automatic update from web-platform-tests Relax feature-detection for <menclose> (#21256) Discussion is still open: w3c/mathml#105 so let's only check some minimal <mrow> support. Igalia does not plan to implement this element in Chromium for now so making detection too strict is causing test failures. -- wpt-commits: ee2b3c3d8740dcfccf6d6a0c5a371335dd198654 wpt-pr: 21256
…a=testonly Automatic update from web-platform-tests Relax feature-detection for <menclose> (#21256) Discussion is still open: w3c/mathml#105 so let's only check some minimal <mrow> support. Igalia does not plan to implement this element in Chromium for now so making detection too strict is causing test failures. -- wpt-commits: ee2b3c3d8740dcfccf6d6a0c5a371335dd198654 wpt-pr: 21256 UltraBlame original commit: 636f59cb8640669c6417462eae91bda7fbd29029
…a=testonly Automatic update from web-platform-tests Relax feature-detection for <menclose> (#21256) Discussion is still open: w3c/mathml#105 so let's only check some minimal <mrow> support. Igalia does not plan to implement this element in Chromium for now so making detection too strict is causing test failures. -- wpt-commits: ee2b3c3d8740dcfccf6d6a0c5a371335dd198654 wpt-pr: 21256 UltraBlame original commit: 636f59cb8640669c6417462eae91bda7fbd29029
This element really needs to be reworked and has been a source of confusion for external people when presenting MathML Core or when writing web platform tests. Let's remove this from the text of the spec for now and current text and discussion to a separate PR. w3c/mathml#105
The fact that "menclose" is present in MathML Core but that there is no plan to implement it in Chromium has been a source of confusion when discussing with externals (TAG, Google, a11y people...) or when writing WPT tests. I've also never been satisfied with the current description which is not as good as the rest of the spec. So moved the current draft into in order to avoid polluting the current text with low-quality WIP things and many "ISSUE" labels. Let's go back to this when the future of menclose is clearer. |
See also #104 and #3
I would like to discuss how much the menclose notations are used, whether they could be replaced with CSS etc
In practice, my feeling is that I've mostly seen (rounded) box and roundedbox (which can be replaced with CSS), updiagonalstrike and circle.
Also, I don't like that some notations are not direction/writing-mode friendly.
I think menclose is the kind of candidate for "custom MathML element" where people could extend mrow with their own drawing of special enclosing/striking notations.
The text was updated successfully, but these errors were encountered: