Closed
Bug 1617585
Opened 6 years ago
Closed 6 years ago
Remove steps 2 and 4 from ProxyCreate
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla77
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: yulia, Assigned: anba)
Details
Attachments
(1 file)
as discussed in: https://github.com/tc39/ecma262/pull/1814
Currently, ProxyCreate is sensitive to whether its arguments are revoked proxies. If either is, it throws a TypeError. This proposal alters the algorithm to remove that sensitivity. Its consequence is that a Proxy could be created successfully where target or handlers are revoked Proxy exotic objects. (It was already possible for such Proxies to exist — just not for them to be created while already in that state.)
We are waiting on tests and editor signoff. This reached consensus in the February 2020.
|
||
Updated•6 years ago
|
Priority: -- → P2
|
Assignee | |
Updated•6 years ago
|
Assignee: nobody → andrebargull
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•6 years ago
|
||
Implements the changes from https://github.com/tc39/ecma262/pull/1814.
Depends on D70814
Pushed by apavel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8c80e8c358d0
Remove the revoked proxy check from ProxyCreate. r=evilpie
|
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in
before you can comment on or make changes to this bug.
Description
•