RESOLVED INVALID 94598
[V8] Move reportUnsafeAccessTo() from V8Proxy to BindingSecurity
https://bugs.webkit.org/show_bug.cgi?id=94598
Summary [V8] Move reportUnsafeAccessTo() from V8Proxy to BindingSecurity
Kentaro Hara
Reported 2012-08-21 07:19:23 PDT
To kill V8Proxy, we can move reportUnsafeAccessTo() from V8Proxy to BindingSecurity.
Attachments
Patch (9.81 KB, patch)
2012-08-21 07:25 PDT, Kentaro Hara
abarth: review-
webkit-ews: commit-queue-
Kentaro Hara
Comment 1 2012-08-21 07:25:09 PDT
Early Warning System Bot
Comment 2 2012-08-21 07:42:37 PDT
Build Bot
Comment 3 2012-08-21 07:48:24 PDT
Early Warning System Bot
Comment 4 2012-08-21 07:51:37 PDT
Gyuyoung Kim
Comment 5 2012-08-21 08:24:12 PDT
Adam Barth
Comment 6 2012-08-21 08:39:48 PDT
Comment on attachment 159685 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=159685&action=review This isn't quite right. BindingSecurity.cpp is part of the "generic bindings", which means it's shared by JavaScriptCore and V8. JavaScriptCore has a much better implementation of this function. I'd like to delete the V8 implementation and share the better JSC implementation. I'll try to get that done in the next day or two. > Source/WebCore/bindings/generic/BindingSecurity.cpp:86 > + Frame* source = firstFrame(BindingState::instance()); The proximate problem is that you can't use BindingState::instance() outside of V8 because in JavaScriptCore, BindingState is the ExecState and JavaScriptCore doesn't keep the ExecState in a static the same way that V8 does.
Kentaro Hara
Comment 7 2012-08-21 09:07:47 PDT
(In reply to comment #6) > This isn't quite right. BindingSecurity.cpp is part of the "generic bindings", which means it's shared by JavaScriptCore and V8. JavaScriptCore has a much better implementation of this function. I'd like to delete the V8 implementation and share the better JSC implementation. I'll try to get that done in the next day or two. Makes sense. Then let me wait for your fix. (I'm not in a hurry:) Marking INVALID.
Note You need to log in before you can comment on or make changes to this bug.