Proxy Support for Private Fields
Categories
(Core :: JavaScript Engine, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: mgaudet, Assigned: mgaudet)
References
(Depends on 1 open bug)
Details
Attachments
(6 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Private fields have some complicated (for the engine to implement) semantics.
Assignee | ||
Comment 1•5 years ago
|
||
The implementation I have with my current patches adds a hidden expando to proxies to support adding private fields to them
In the Chome(/Edge Beta) devtools, when you stamp a private field onto a proxy, you can inspect it. I think we'll need to open a bug later to do the same thing.
Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D83145
Assignee | ||
Comment 4•5 years ago
|
||
Depends on D83146
Assignee | ||
Comment 5•5 years ago
|
||
Depends on D83147
Assignee | ||
Comment 6•5 years ago
|
||
- CrossOriginWrappers
- A variety DOM objects (including window, and window's prototype chain)
- Xray wrappers
I am seeking advice with this for pointers on how to test other proxy types
I think am aware of:
- Cross Process Object Wrappers
as well as those I am not aware of.
Depends on D83511
Assignee | ||
Comment 7•5 years ago
|
||
Depends on D83555
Assignee | ||
Updated•5 years ago
|
Comment 9•5 years ago
|
||
Backed out for failure at proxy-ccw.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/b1d2d66897f8480dda540ff2507f836c24b5fd42
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=310379859&repo=autoland&lineNumber=7539
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 10•5 years ago
|
||
So, Tom did mention on IRC that it's not -amazing- that we're increasing the number of slots on DOM proxies; I tend to agree, but don't think it's worth blocking landing this. AWSY results are fairly inconclusive.
Comment 11•5 years ago
|
||
Comment 12•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 13•5 years ago
|
||
![]() |
||
Comment 14•5 years ago
|
||
bugherder |
Description
•