-
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
"small" "normal" "big" values of mathsize #7
Comments
See also #4 |
MathML Core does not really define mathsize yet, but the schema currently mentions these values. |
The values were removed from the MathML schema in w3c/mathml-core@bbc0f8a ; we agreed not to add them back to core. I'm leaving this open because it still remains to:
|
Decision is to keep in MathML full but note in main spec that non core features will require polyfills so you may not want to use them. https://lists.w3.org/Archives/Public/public-mathml4/2019Mar/0026.html |
Resolution: Specification:
Implementation:
Polyfill:
Tests:
|
MathPlayer uses the values: 0.8, 1.0, 1.25 for small, normal, big, respectively. Note: specification of mathsize takes priority over fontsize. |
These are not in core ( #7 (comment) ) ; @davidcarlisle can you please check full and update it if needed? |
MathJax uses the values 0.71, 1, 2 for small, normal, big, respectively. |
WebKit uses values 0.75em, 1em and 1.5em: Firefox uses the keyword "small", "medium", "large": As specified in https://drafts.csswg.org/css-fonts-3/#font-size-prop I think it makes sense for a CSS-based polyfill to use font-size keyword "small", "medium", "large" so that the scaling factor is up to the browser and consistent with CSS. |
Here are the values I used the last time I looked at this (pre-2011, at least) |
The proposal we had in previous meeting was to set this in MathML full:
|
https://lists.w3.org/Archives/Public/public-mathml4/2019Jun/0013.html ADOPTED Mapping to CSS’s values for x-small (¾), medium (1), and x-large |
These values have been removed from MathML Core ( w3c/mathml#7 )
These values have been removed from MathML Core ( w3c/mathml#7 )
Test landed: web-platform-tests/wpt#18037 I'm closing this since the remaining work is in implementation (native or polyfill) |
…ze values, a=testonly Automatic update from web-platform-tests MathML: Add tests to check legacy mathsize values (#18037) These values have been removed from MathML Core ( w3c/mathml#7 ) -- wpt-commits: 54f7b9af46a8a8b6e9d43907d19d3250cbfbc83e wpt-pr: 18037
…ze values, a=testonly Automatic update from web-platform-tests MathML: Add tests to check legacy mathsize values (#18037) These values have been removed from MathML Core ( w3c/mathml#7 ) -- wpt-commits: 54f7b9af46a8a8b6e9d43907d19d3250cbfbc83e wpt-pr: 18037
Polyfill:
|
See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1548527 gecko-commit: 3bfee29aef8e9babb5a6c1cb02a78a32a68f9b0c gecko-integration-branch: autoland gecko-reviewers: emilio
…thsize attribute. r=emilio See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 --HG-- extra : moz-landing-system : lando
…te. (#18553) See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1548527 gecko-commit: 3bfee29aef8e9babb5a6c1cb02a78a32a68f9b0c gecko-integration-branch: autoland gecko-reviewers: emilio
…thsize attribute. r=emilio See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426
…#18037) These values have been removed from MathML Core ( w3c/mathml#7 )
…te. (web-platform-tests#18553) See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1548527 gecko-commit: 3bfee29aef8e9babb5a6c1cb02a78a32a68f9b0c gecko-integration-branch: autoland gecko-reviewers: emilio
…ze values, a=testonly Automatic update from web-platform-tests MathML: Add tests to check legacy mathsize values (#18037) These values have been removed from MathML Core ( w3c/mathml#7 ) -- wpt-commits: 54f7b9af46a8a8b6e9d43907d19d3250cbfbc83e wpt-pr: 18037 UltraBlame original commit: 5bab6e8de4f5cb67ea8763ca35676595070b97d7
…thsize attribute. r=emilio See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 UltraBlame original commit: 3bfee29aef8e9babb5a6c1cb02a78a32a68f9b0c
…ze values, a=testonly Automatic update from web-platform-tests MathML: Add tests to check legacy mathsize values (#18037) These values have been removed from MathML Core ( w3c/mathml#7 ) -- wpt-commits: 54f7b9af46a8a8b6e9d43907d19d3250cbfbc83e wpt-pr: 18037 UltraBlame original commit: 5bab6e8de4f5cb67ea8763ca35676595070b97d7
…ze values, a=testonly Automatic update from web-platform-tests MathML: Add tests to check legacy mathsize values (#18037) These values have been removed from MathML Core ( w3c/mathml#7 ) -- wpt-commits: 54f7b9af46a8a8b6e9d43907d19d3250cbfbc83e wpt-pr: 18037 UltraBlame original commit: 5bab6e8de4f5cb67ea8763ca35676595070b97d7
…thsize attribute. r=emilio See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 UltraBlame original commit: 3bfee29aef8e9babb5a6c1cb02a78a32a68f9b0c
…thsize attribute. r=emilio See w3c/mathml#7 and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kyB34PjYXek This commit introduces a new preference option mathml.mathsize_names.disabled to disable mathsize keyword values. For now, these are only disabled in Nightly builds. * test_bug553917.html is updated to check that these values now cause an error message to be logged into the console when mathsize names are used and the feature disabled. * The old test 355548-3.xml checks support for mathsize names and also uses several features that are going to be deprecated. So it is just run with the proper preference adjustment. * mathml/relations/css-styling/mathsize-attribute-legacy-values.html passes after this change so the test is run with the mathsize names disabled too and the failure expectation is removed. * mathml/relations/css-styling/mathsize-attribute-css-keywords.html is added to check that CSS keywords won't be supported when we switch to using the CSS parser in the future. This test passes now when the "small" keyword is not accepted so it is run with the mathsize names disabled too. Differential Revision: https://phabricator.services.mozilla.com/D42426 UltraBlame original commit: 3bfee29aef8e9babb5a6c1cb02a78a32a68f9b0c
The proposal is to remove/deprecate these attribute values.
In any case "small" and "big" values are NOT accurately specified:
"The values "small" and "big" choose a size smaller or larger than the current font size, but leave the exact proportions unspecified; "normal" is allowed for completeness, but since it is equivalent to "100%" or "1em", it has no effect. "
The text was updated successfully, but these errors were encountered: