Trimming of whitespace in attribute
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 56
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
This was mentioned in w3c/mathml#63
From https://w3c.github.io/mathml/#syntax-notation-used-in-the-mathml-specification :
"Since some applications are inconsistent about normalization of whitespace, for maximum interoperability it is advisable to use only a single whitespace character for separating parts of a value. Moreover, leading and trailing whitespace in attribute values should be avoided."
Currently MathML Core does not say anything about leading/trailing whitespace in attributes. I think we should be explicit about this. Do we allow them or not?
The non-normative RelaxNG schema is inconsistent ( https://github.com/mathml-refresh/mathml-schema/tree/master/rnc ), sometimes they are allowed, sometimes they are not.
Reminder: In w3c/mathml#21 we agree to align definition on HTML5/CSS.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the MathML Core specification context and the linked w3c/mathml#63 and w3c/mathml#21 discussions first. Compare the non-normative RelaxNG schema in the mathml-schema repository, then establish whether leading and trailing attribute whitespace is allowed and update the specification and schema consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100