[heycam/webidl] Standardize around typography of IDL true/false/null (#457)

I kept certain constants bolded in the spec for readability. The distinction is basically summarized in the updated Document Conventions:

> * IDL types: `unsigned long`
> * IDL values: true, false, null, 0.42, −0
> * ECMAScript classes: `Map`
> * ECMAScript language types: Object
> * ECMAScript values: generally the same notation as IDL values; bolded type (e.g. **true**) may be used when it is needed to distinguish between ECMAScript and IDL values, or if the ECMAScript value does not have a single corresponding IDL value of the same name (**undefined** and **NaN**).

The last bullet point is especially needed for things like:

> The IDL `boolean` value true is converted to the ECMAScript **true** value and the IDL boolean value false is converted to the ECMAScript **false** value.

which IMO looks odd with either both bolded or both regular-weighted. Also, ECMAScript true is usually not bolded for things like

> The property has the attributes { [[Writable]]: true, [[Enumerable]]: false, [[Configurable]]: true }.

.

Happy to have a discussion about it.

Fixes #437.
You can view, comment on, or merge this pull request online at:

  https://github.com/heycam/webidl/pull/457

-- Commit Summary --

  * Standardize around typography of IDL true/false/null
  * Fix linking warning

-- File Changes --

    M index.bs (350)

-- Patch Links --

https://github.com/heycam/webidl/pull/457.patch
https://github.com/heycam/webidl/pull/457.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/pull/457