Commit b904ab59 authored by antonm@chromium.org's avatar antonm@chromium.org

2011-02-08 Anton Muhin <antonm@chromium.org>

       Reviewed by Adam Barth and Alexey Proskuryakov.

       Propagate security origin of parent document into HTML documents created with DOMImplementation
       https://bugs.webkit.org/show_bug.cgi?id=53611

       This restores invariant that JS wrappers residing in the same JS context should come
       from the same security origin.

       Absence of regressions is covered by the current tests.  Different security origin of
       DOMImplementation is difficult to check with layout tests as DOMImplementation
       resides in the same JS context as parent document and therefore there are no security origin checks.
       This is observable however in C++.

       * Android.jscbindings.mk:
       * CMakeLists.txt:
       * WebCore.gypi:
       * WebCore.pro:
       * WebCore.vcproj/WebCore.vcproj:
       * WebCore.xcodeproj/project.pbxproj:
       * bindings/v8/V8GCController.cpp:
       (WebCore::NodeGrouperVisitor::visitDOMWrapper):
       * dom/DOMImplementation.cpp:
       (WebCore::DOMImplementation::DOMImplementation):
       (WebCore::DOMImplementation::createDocument):
       * dom/DOMImplementation.h:
       (WebCore::DOMImplementation::create):
       (WebCore::DOMImplementation::documentDestroyed):
       (WebCore::DOMImplementation::parentDocument):
       * dom/DOMImplementation.idl:
       * dom/Document.cpp:
       (WebCore::Document::~Document):
       (WebCore::Document::implementation):
       * dom/Document.h:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@86423 268f45cc-cd09-0410-ab3c-d52691b4dbfc
parent f9c19cc4
2011-05-12 Anton Muhin <antonnm@chromium.org>
Unreviewed.
Rebaselining tests under r86417.
2011-05-05 Hans Wennborg <hans@chromium.org> 2011-05-05 Hans Wennborg <hans@chromium.org>
Reviewed by Steve Block. Reviewed by Steve Block.
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong content-type isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong signature isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong signature isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong content-type isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong signature isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong signature isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a redirect makes resource caching fail.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong content-type isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong signature isn't treated as such.
Should say SUCCESS:
SUCCESS
Test that a manifest served with a wrong signature isn't treated as such.
Should say SUCCESS:
SUCCESS
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment