Skip to content

Commit d51401f

Browse files
authored
Update README.md
1 parent 5d4bb9b commit d51401f

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,7 @@ V8 has has a non-standard [Stack Trace API](https://v8.dev/docs/stack-trace-api)
99

1010
In August 2023, [JSC also shipped this method](https://github.com/WebKit/WebKit/commit/997e074bb35ed07b69c9b821141c91dd548e0d02)
1111

12-
Has now turned into a web-compatability problem, and as a result it is time it
13-
is standardized.
12+
This method [has now turned into a web-compatability problem](https://bugzilla.mozilla.org/show_bug.cgi?id=1886820), and as a result we should now standardize it.
1413

1514
## `Error.captureStackTrace`
1615

@@ -47,4 +46,4 @@ I would actually like to specify this like the JSC one. It's simpler. Similarly,
4746

4847
## Related Work
4948

50-
- The [Error Stacks](https://github.com/mgaudet/proposal-error-capturestacktrace) proposal is almost a pre-requisite for this, as mostly the current spec doesn't really talk about stacks. However, for this proposal I'd argue
49+
- The [Error Stacks](https://github.com/mgaudet/proposal-error-capturestacktrace) proposal is largely an orthogonal one to this, but it would provide framework and text to talk about stack strings, as mostly the current spec doesn't really talk about stacks. However, for this proposal I'd argue we don't need to specify the contents of stack strings.

0 commit comments

Comments
 (0)