Re: [heycam/webidl] Modernize invoking user code (#113)

OK, @bzbarsky, this is ready for you to take a look at. https://rawgit.com/domenic/webidl/07ffceee1adb2e0c03ec1fc8a0c8eda94e4da219/index.html#es-user-objects should be a viewable version of the output.

Some notes:

- I went the extra distance and re-did all the abrupt completion stuff, in preparation for fixing all the "report an exception" stuff. This mostly seems better. Although it's sometimes a bit strange that we have ES completion values containing IDL values, I think that's how it has to be.
- I haven't tried tightening the promise language yet (e.g. introducing to ES a "CreateRejectedPromise" operation). We'll leave that for "some day".
- This does not yet fix incumbent settings objects. My current queue on all this mess looks like:
  - Get this PR merged, in order to fix entry settings objects
  - Get https://github.com/whatwg/html/pull/1189 merged, in order to lay the groundwork for fixing incumbent settings objects
  - Do a new Web IDL PR that adds a few steps in order to fix incumbent settings objects
  - Fix https://github.com/whatwg/html/issues/855 to take care of incumbent/entry settings objects in places like StructuredClone
  - Fix "report an exception" as discussed in steps 2-4 above.
  - Go triage and test all uses of incumbent and entry in various specs to see if we can get rid of them in favor of current.

---
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/113#issuecomment-218883109