Summary: | Promise.prototype.then should use Symbol.species to construct the return Promise | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Keith Miller <keith_miller> | ||||
Component: | New Bugs | Assignee: | Keith Miller <keith_miller> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue, mark.lam, msaboff, saam | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Keith Miller
2016-03-01 10:33:59 PST
Created attachment 272575 [details]
Patch
Comment on attachment 272575 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=272575&action=review > Source/JavaScriptCore/builtins/PromisePrototype.js:46 > + var constructor = constructor[@symbolSpecies]; Style: remove the "var" here. > Source/JavaScriptCore/builtins/PromisePrototype.js:47 > + if (constructor == null) Is this "==" instead of "===" on purpose for null/undefined case? Comment on attachment 272575 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=272575&action=review >> Source/JavaScriptCore/builtins/PromisePrototype.js:46 >> + var constructor = constructor[@symbolSpecies]; > > Style: remove the "var" here. fixed. >> Source/JavaScriptCore/builtins/PromisePrototype.js:47 >> + if (constructor == null) > > Is this "==" instead of "===" on purpose for null/undefined case? Yeah. Committed r197428: <http://trac.webkit.org/changeset/197428> |