Editorial: formalize reflect's default value

[annevk]

And rename some number-related options to be less verbose and more consistent.

Fixes #8926 and fixes #8927.

---

/common-dom-interfaces.html ( diff )
/form-elements.html ( diff )
/grouping-content.html ( diff )
/input.html ( diff )
/interaction.html ( diff )
/obsolete.html ( diff )
/tables.html ( diff )

[domenic]

Nice, I like especially how this gives us back-links to the "default value" term from the reflected IDL attribute declarations.

[tabatkins]

I still think "positive", by itself, is ambiguous. Can I suggest "positive non-zero" again?

[domenic]

I strongly disagree that's it's ambiguous. Positive is defined as > 0. Positive and non-negative are clearly non-overlapping categories.

[tabatkins]

And like I said in my linked comment, that is not true, particularly in the context of the web platform. JS's zero is positive or negative, not unsigned, for example. (Even Math.sign() agrees, as it turns out, since it actually has four possible results: +1, -1, +0, or -0.)

We've had confusion about this exact issue in CSS in the past. I'm not sure if we're 100% consistent, but I know I have rewritten text to be more explicit, at the request of readers who were genuinely unsure.

[annevk]

These terms are defined in a way that is unambiguous. In Infra we can take that a step further once we get around to numbers.