Conversation
37b4f60 to
17d9044
Compare
17d9044 to
b95c824
Compare
b95c824 to
3ad18be
Compare
|
I've split out all the fixes you requested that aren't part of this PR, but are instead part of #1668, into a separate commit. Please only review the last commit here :-) |
|
Sorry, I wasn't paying enough attention (re #1668). |
3ad18be to
5349602
Compare
5349602 to
e3c5cd5
Compare
e3c5cd5 to
d113e4f
Compare
d113e4f to
d7c3c84
Compare
d7c3c84 to
da72c39
Compare
|
No? It's only the class which is able to do this check; you can't write |
|
@WebReflection |
|
OK, the class “owns” the private field access, but I wonder what a Proxy trap would do there, and if this check could lead to “leaking” exploits. If Proxy can’t intercept these check then fine, but I didn’t read anything about proxies in the text. If I missed that, no issue, if I didn’t, are private fields leaking via Proxy traps? |
|
@WebReflection Proxy has no ability to detect or intercept private fields, or internal slots. If there's further discussion to be had, can we have it in the discourse or on the proposal repo, instead of here on the spec PR? |
|
Thanks! Please ignore my comments then, I had a mix of a-aha and “the heck?” moment there. All good 👍 |
791f910 to
c274ab1
Compare
c274ab1 to
b1911ec
Compare
b1911ec to
de8ba37
Compare
de8ba37 to
66a3f9e
Compare
66a3f9e to
f9f006c
Compare
f9f006c to
a060ea8
Compare
a060ea8 to
e172a6e
Compare
This PR is based on top of #1668. Please review by commit. As #1668 is updated and/or merged, I'll rebase this one.