Skip to content
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

Clarify formatting specifiers a bit #25

Closed
domenic opened this issue Jan 10, 2016 · 2 comments
Closed

Clarify formatting specifiers a bit #25

domenic opened this issue Jan 10, 2016 · 2 comments

Comments

@domenic
Copy link
Member

domenic commented Jan 10, 2016

Right now the section https://console.spec.whatwg.org/#formatting-specifiers is kind of disconnected from the main text. https://console.spec.whatwg.org/#formatter handles some of them, but the ones that require complex UI are ignored by the rest of the spec's algorithms.

I am not sure how best to reconcile this. Maybe Formatter() should reference the tables in #formatting-specifiers, and remove the algorithm steps? Maybe Formatter() should get an additional line for each of %o, %O, or %c? But these don't act like type conversions, exactly...

In any case one goal should be to ensure there is only one normative source of truth---either the algorithm or the tables. If we decide on the algorithm being normative, then we can keep the tables, we just need to mark them non-normative.

@terinjokes
Copy link
Collaborator

My vote would be to have the algorithms as normative and have the tables as non-normative reference.

@robertkowalski
Copy link
Member

i agree with terin, i would also prefer that and also mentioned it in #6 (comment)

domenic added a commit that referenced this issue Jan 28, 2016
Closes #25. Closes #36 by incorporating @paulirish's feedback that %o is a bit more generic than "expandable DOM object". Closes #33 by superceding it.
domenic added a commit that referenced this issue Jan 28, 2016
Closes #25. Closes #36 by incorporating @paulirish's feedback that %o is a bit more generic than "expandable DOM object". Closes #33 by superseding it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants