[w3c/manifest] Added CatchTypeError to all fields of WebAppManifest and other places. (#750)

**DO NOT SUBMIT** just yet. Depends upon heycam/webidl#597 so I'm just posting this as a request for comments.

Closes #611.

This change (choose one):

* [X] Breaks existing normative behavior (please add label "breaking")
* [ ] Adds new normative requirements
* [ ] Adds new normative recommendations or optional items
* [ ] Makes only editorial changes (only changes informative sections, or
  changes normative sections without changing behavior)
* [ ] Is a "chore" (metadata, formatting, fixing warnings, etc).

**However**, while this is marked as breaking, I suspect this reverts a previous breakage back to the previous behaviour (members with type errors invalidate just the member, not the whole manifest). I'll have to investigate the old text and other implementations. The goal of this is to *improve* spec compatibility with implementations.

Implementation commitment (delete if not making normative changes):

* [ ] Safari (link to issue)
* [ ] Chrome (link to issue)
* [ ] Firefox (link to issue)
* [ ] Edge (public signal)

Commit message:

This restores the previous behaviour (before we switched to WebIDL)
where individual elements being a type error would not invalidate the
whole manifest.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/manifest/pull/750

-- Commit Summary --

  * Added CatchTypeError to all fields of WebAppManifest and other places.

-- File Changes --

    M index.html (37)

-- Patch Links --

https://github.com/w3c/manifest/pull/750.patch
https://github.com/w3c/manifest/pull/750.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/w3c/manifest/pull/750