Bug 225328
Summary: | Web Inspector: PromiseStatus should be "fulfilled", not "resolved" | ||
---|---|---|---|
Product: | WebKit | Reporter: | bugmenot |
Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | inspector-bugzilla-changes, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | All | ||
OS: | All |
bugmenot
Seems like nobody filled an issue for Safari yet. Quoting from the now closed Chromium bug:
According to spec, and docs online, "An unresolved promise is always in the pending state. A resolved promise may be pending, fulfilled or rejected."
http://www.ecma-international.org/ecma-262/6.0/#sec-promise-objects
V8 generates internal property [[PromiseStatus]], which is pending, resolved, or rejected. It seems more correct for 'resolved' to be renamed to 'fulfilled'.
See:
https://bugs.chromium.org/p/v8/issues/detail?id=6751
https://twitter.com/jaffathecake/status/1248179232775319559
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/77781649>
Cheng You Bai (:cybai)
Pull request: https://github.com/WebKit/WebKit/pull/15544
EWS
Committed 266058@main (359976cda05e): <https://commits.webkit.org/266058@main>
Reviewed commits have been landed. Closing PR #15544 and removing active labels.