Re: [spec-reviews] Promise rejection tracking events (#96)

> Is the specified weak set of unhandled promise rejections exposed to script anywhere? If not, why are its semantics so tightly (un)specified?

The weak set is a tracking mechanism for what unhandledrejection events have been fired, basically, so that later rejectionhandled events can correspond to them. So the contents are exposed to script, somewhat indirectly. Does that help?

> Lastly, it's unclear why the spec is explicit about when/where things are reported to developer consoles. It seems out of scope for normative text.

This was modeled after synchronous errors and the error event, which say:

> When the user agent is to report an exception E, the user agent must report the error for the relevant script, with the problematic position (line number and column number) in the resource containing the script, using the global object specified by the script's settings object as the target. **If the error is still not handled after this, then the error may be reported to the user.**

I think I meant to consistify both of these to say "developer console" per https://github.com/whatwg/html/pull/224#discussion_r43070230 but I forgot to go back and change the onerror one. I'll do that now.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/96#issuecomment-165247219