Skip to content

Fix some typos and broken links #55

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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Fix some typos and broken links #55

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
19acffa
Remove extra parenthesis.
edent Oct 11, 2025
b98cee1
Standardise links in README
edent Oct 11, 2025
f16adac
Fix broken link
edent Oct 11, 2025
143cf05
Fix broken Twitter link
edent Oct 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,14 +11,14 @@ In general we expect to focus on developing explainers that:
* or a counterproposal that is more aligned with the Web Vision than existing technologies or proposals

## Current Explainers
* [EyeDropper as <input>](https://github.com/mozilla/explainers/blob/main/eyedropper-input.md)
* [Amount](https://github.com/mozilla/explainers/blob/main/amount.md)
* [EyeDropper as <input>](eyedropper-input.md)
* [Amount](amount.md)
* [Translation API](translation.md)
* [Standard Measures with U.S. English](standard-measures-en-us.md)
* ...

## Feedback on Explainers
We strongly prefer external feedback only on explainers that are in their own repo (see [Explainer file progress](#explainer-file-progress)).
We strongly prefer external feedback only on explainers that are in their own repo (see [Explainer repo progress](#explainer-repo-progress)).

If you see something in a Mozilla Explainer that you want to suggest changing or fixing, please file an issue describing the problem and suggested resolution, not a pull request.
Exception: minor non-substantive or typographical changes may be submitted as PRs.
Expand Down
4 changes: 2 additions & 2 deletions amount.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Both elements are also widely natively supported by browsers
([MDN data support](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/data#browser_compatibility),
[MDN time support](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time#browser_compatibility)),
however without any default user-discernible effects,
including [in screen readers](https://twitter.com/LeonieWatson/status/1333078194925264898),
including [in screen readers]([https://twitter.com/LeonieWatson/status/1333078194925264898](https://web.archive.org/web/20201129160223/https://twitter.com/LeonieWatson/status/1333078194925264898)),
despite the “[First rule of ARIA use](https://www.w3.org/TR/aria-in-html/#rule1)” encouraging publishers to use native HTML semantic elements.

### Prior proposals
Expand Down Expand Up @@ -132,7 +132,7 @@ Proposal: a new HTML `<amount>` element (similar to `<data>` and `<time>`), with

### currency extension
As an exploration, to extend the `<amount>` element to support currency, we could do so with:
* `currency` attribute: optional currency code (([ISO 4217](https://en.wikipedia.org/wiki/ISO_4217)) to express a monetary amount. User agents could use an online exchange service to compute rough equivalents and note the source and time dependency (temporal context) of any such conversions.
* `currency` attribute: optional currency code ([ISO 4217](https://en.wikipedia.org/wiki/ISO_4217)) to express a monetary amount. User agents could use an online exchange service to compute rough equivalents and note the source and time dependency (temporal context) of any such conversions.
* e.g. `<amount currency=USD value=64000>$64,000</amount>`
* The presence of both `unit` and `currency` attributes is an error. The user agent must ignore both attributes.
* Quantity change: If neither a unit (attribute or parsed) nor `currency` attribute are present, the amount is unitless and expresses a quantity.