Extensions are not a feature of webkit, they are a feature of the
browser, so it seems strange that tests for them would exist in the
webkit repository.
If this isolated world concept was not specific to chromium -- eg. it
was being exposed potentially as a "sandboxing" api for web content
such that a page would be able provide an execution context for
untrusted executable content, but this sounds like it is specifically
for extensions in a webkit client application.
--Oliver
On Jul 1, 2009, at 4:53 PM, Adam Barth wrote:
Hi webkit-dev,
I'm working on a security feature so that Chromium extensions can run
their content scripts in an "isolated world" separate from the main
page's JavaScript objects. I'm about to start writing a bunch of
tests for the feature, and I'd like some advice about where to put the
tests. Some candidate places are:
1) LayoutTests/http/tests/security/isolatedWorld
2) LayoutTests/platform/chromium/http/tests/security/isolatedWorld
3) Somewhere in the chromium.org source tree
Most (all?) of the implementation work will take place in
WebCore/bindings/v8. The tests will rely on a magical
layoutTestController function with a name like
"evaluateInIsolatedWorld." The feature isn't specific to Chromium in
the sense that one could imagine implementing the same thing in the
JSC bindings if a JSC port wanted to support these kinds of
extensions, but it's not completely general either in the sense that
it's not currently part of the web platform.
I slightly prefer option (1), but I'll defer to consensus opinion.
Thanks!
Adam
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
