Path to Stage 4!

[ljharb]

Stage 4

• committee approval
• two implementations
  • v8 (node / Chrome)
  • node (for DOMException)
  • spidermonkey (Firefox)
  • jsc (Webkit / Safari)
  • Deno (for DOMException)
  • Porffor
  • es-shims polyfill
  • keisel
  • Boa
• significant in-the-field experience
• ecma262 PR approved
• prepare ecma262 PR
• HTML integration PRs merged (web platform integration #8)
  • HTML integration for "Error Stack Accessor" TC39 Proposal whatwg/html#12239
  • Update DOMException language to reflect standardized stack accessor whatwg/webidl#1578
  • Add WPT tests for Error Stack Accessor proposal web platform integration web-platform-tests/wpt#58397

Stage 3

• committee approval
• merge test262 tests
• write test262 tests
• HTML integration PRs approved (web platform integration #8)
  • HTML integration for "Error Stack Accessor" TC39 Proposal whatwg/html#12239
  • Update DOMException language to reflect standardized stack accessor whatwg/webidl#1578
  • Add WPT tests for Error Stack Accessor proposal web platform integration web-platform-tests/wpt#58397

Stage 2.7

• committee approval
• spec editor signoff
  • @syg
  • @bakkot
• spec reviewer signoff
  • @michaelficarra
  • @nicolo-ribaudo
• Feedback on web compatibility #10 / The Setter probably should still define without ErrorData slot.  #2 (spec the setter)
• Should setter throw for non-strings? #6
• ensure the getter does not throw for non-errors (Feedback on web compatibility #10)
• Should the stack getter on a non-Error return undefined or an empty string? #3

Stage 2

• committee approval
• spec reviewers selected
• spec text written

Stage 1

• committee approval

[michaelficarra]

In §20.5.4 Properties of Error Instances, there's

The only specified use of [[ErrorData]] is to identify Error, AggregateError, and NativeError instances as Error objects within Object.prototype.toString and Error.isError.

This needs to be updated. There's similar claims in the summaries of the NativeError and AggregateError constructors that also need to be updated.

[nicolo-ribaudo]

The proposal's spec text looks good to me.

[bakkot]

The setter's a bit weird, but assuming that's definitely the behavior we want, LGTM.

[ljharb]

Fixed Michael's comment in #9 (comment).