Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upFixing description of [[thisMode]] internal slot of Function Object. #1305
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ljharb
Sep 12, 2018
Member
Indeed, in step 6.a of https://tc39.github.io/ecma262/#sec-ordinarycallbindthis it checks undefined or null; which suggests that the text in https://tc39.github.io/ecma262/#table-27 should be changed from "undefined" to "undefined or null".
|
Indeed, in step 6.a of https://tc39.github.io/ecma262/#sec-ordinarycallbindthis it checks undefined or null; which suggests that the text in https://tc39.github.io/ecma262/#table-27 should be changed from "undefined" to "undefined or null". |
ljharb
added
editorial change
spec bug
good first patch
labels
Sep 12, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ENvironmentSet
Sep 15, 2018
and, another one about this.
in step 6.b.i of OrdinaryCallBindThis it convert primitive value to Object. we may add information about this too.
ENvironmentSet
commented
Sep 15, 2018
|
and, another one about this. in step 6.b.i of OrdinaryCallBindThis it convert primitive value to Object. we may add information about this too. |
ENvironmentSet commentedSep 12, 2018
in current, specification explain
[[thisMode]]of Function Object as blow.and I think, this line missed some action about how global this mode works.
because, In
OrdinaryCallBindThisabstract operation that used to bindthisvalue into function environment record. It interpretnullas reference to global object likeundefined.So, In my opinion, changing that line to blow will make more clear specification.