Closed Bug 1548522 Opened 7 months ago Closed Last month

Remove support for the menclose's "radical" notation

Categories

(Core :: MathML, task)

task
Not set

Tracking

()

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: fredw, Assigned: fredw)

References

(Blocks 1 open bug, )

Details

(Keywords: dev-doc-needed, site-compat)

Attachments

(2 files)

The MathML CG agrees to drop it from MathML Core, it duplicates the <msqrt> element and is not used in practice: https://github.com/mathml-refresh/mathml/issues/3#issuecomment-475507647

Assignee: nobody → fred.wang
Status: NEW → ASSIGNED
Attachment #9094441 - Flags: data-review?(bmiroglio)
Keywords: site-compat

See https://groups.google.com/forum/#!topic/mozilla.dev.platform/vwAkuZIEhnY

This is WIP, I think handling of invalid values is not clear in the core spec.
See https://github.com/mathml-refresh/mathml/issues/144

  • Introduce a new preference option to disable menclose's "radical" notation.
  • Disable the notation in Nightly and when running WPT tests.
  • Enable the notation in other channels together with a counter and
    deprecation warning.
  • Remove failure expectation for WPT test legacy-menclose-radical-notation.html
  • Enable the radical notation for MathML reftests testing it.
Comment on attachment 9094441 [details]
data-collection-mathml-menclose-radical-notation.txt

# Data Review Form 

1) Is there or will there be **documentation** that describes the schema for the ultimate data set in a public, complete, and accurate way? (see [here](https://github.com/mozilla/activity-stream/blob/master/docs/v2-system-addon/data_dictionary.md), [here](https://github.com/mozilla-mobile/focus/wiki/Install-and-event-tracking-with-the-Adjust-SDK), and [here](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/index.html) for examples).  Refer to the appendix for "documentation" if more detail about documentation standards is needed.

This will be documented in the [probe dictionary](https://telemetry.mozilla.org/probe-dictionary/).

2) Is there a control mechanism that allows the user to turn the data collection on and off? (Note, for data collection not needed for security purposes, Mozilla provides such a control mechanism) Provide details as to the control mechanism available.

Yes, this can be turned off in Firefox Preferences.

3) If the request is for permanent data collection, is there someone who will monitor the data over time?

This is not permanent, although there's the potential for renewal. :fredw is responsible should a renewal be necessary.

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1: Technical Data

5) Is the data collection request for default-on or default-off?

default-on

6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc.  See the appendix for more details)?

No.

7) Is the data collection covered by the existing Firefox privacy notice? 

Yes.

8) Does there need to be a check-in in the future to determine whether to renew the data? 

Yes. In 6 months :fredw should check in.

9) Does the data collection use a third-party collection tool? **If yes, escalate to legal.**

No.

data-review: r+
Attachment #9094441 - Flags: data-review?(bmiroglio) → data-review+
Attachment #9094443 - Attachment description: Bug 1548522 - Remove support for the menclose's "radical" notation. → Bug 1548522 - Remove support for the menclose's "radical" notation. r=emilio

Pushed by csabou@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d2613eaa1369
Remove support for the menclose's "radical" notation. r=emilio

Keywords: checkin-needed
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/19495 for changes under testing/web-platform/tests
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.
Upstream PR was closed without merging
Backout by csabou@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8d5b29ee19f3
Backed out changeset d2613eaa1369 for reftest failures on legacy-menclose-radical-notation.html.

mmh, I don't understand why it was not caught by the try server. But the first menclose of legacy-menclose-radical-notation-ref.html should be <menclose notation="">

Flags: needinfo?(fred.wang)

(In reply to Frédéric Wang (:fredw) from comment #11)

mmh, I don't understand why it was not caught by the try server. But the first menclose of legacy-menclose-radical-notation-ref.html should be <menclose notation="">

mmh, this was even written in the commit message. Not sure how I overlooked it.

Keywords: checkin-needed

Pushed by csabou@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6d734cb4e0ca
Remove support for the menclose's "radical" notation. r=emilio

Keywords: checkin-needed
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.
Status: ASSIGNED → RESOLVED
Closed: Last month
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.