w3c / w3c/mathml-core

Impact and strategy for polyfills

Open
#263 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

meta-tracking
Dominant language
HTML
Stars
56
Forks
20
PR merge metrics
No merged PRs in 30d

Description

In the various discussions on deprecating and simplifying the various features, elements and attributes of MathML, as well as whether or not a given feature should be present in MathML Core, one of the key factors in the decision is whether the feature in question can be recovered by use of a polyfill. I would like to start a discussion about how the group envisions polyfills being used.

For purpose of argument, let us assume that every feature in in the main spec but missing from Core would/could be implemented by a polyfill. We would need appropriate Feature Detection for each feature as well, which seems in some cases harder than the polyfill itself(?)

  • Is including polyfills an author or browser responsibility?
  • Would there be a standard set of feature/polyfill pairs?
  • A master polyfill?
  • A method to determine which polyfills are needed?
  • General questions about performance trade-offs (both rendering and network).
    Presumably more questions will arise as we discuss :>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the issue's questions alongside the MathML Core and deprecation discussions it references. A useful outcome would be a documented group position on author versus browser responsibility, feature detection, standard polyfill sets, and performance trade-offs; no specific files or tests are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.