offlineasm has some impossible to implement, and unused, instructions
https://bugs.webkit.org/show_bug.cgi?id=96310

Reviewed by Mark Hahnenberg.

* offlineasm/armv7.rb:
* offlineasm/instructions.rb:
* offlineasm/x86.rb:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128100 268f45cc-cd09-0410-ab3c-d52691b4dbfc
        [WK2] Add an API to open a page in same process
        https://bugs.webkit.org/show_bug.cgi?id=96306

        Reviewed by Anders Carlsson.

        The name "related" inspired by <http://wiki.whatwg.org/wiki/Links_to_Unrelated_Browsing_Contexts>.

        * UIProcess/API/mac/WKView.h: Added an API. It's unwieldy, but I blame
        WKBrowsingContextGroup, not the related view.

        * UIProcess/API/mac/WKViewPrivate.h: Matching SPI for clients that mostly use
        C APIs.

        * UIProcess/API/mac/WKView.mm:
        (-[WKView initWithFrame:processGroup:browsingContextGroup:]): Use new back-end
        signature.
        (-[WKView initWithFrame:processGroup:browsingContextGroup:relatedToView:]):
        Get page from WKView, and call back-end.
        (-[WKView initWithFrame:contextRef:pageGroupRef:]): Reimplement existing method
        by calling new, more powerful one.
        (-[WKView initWithFrame:contextRef:pageGroupRef:relatedToPage:]): Just one change,
        pass relatedPage to the context.

        * UIProcess/WebContext.cpp: (WebKit::WebContext::createWebPage): If related page
        is not null, use its process.

        * UIProcess/WebContext.h: (WebContext): Updated createWebPage signature.



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128101 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[V8] setNamedHiddenWindowReference doesn't need to be a special case
https://bugs.webkit.org/show_bug.cgi?id=96198

Reviewed by Nate Chapin.

Prior to this patch, the DOMWindow cached its properties on the outter
global object rather than on the Holder of the properties. (We cache
properties to prevent their DOM wrappers from being garbage collected
too early.) There doesn't seem to be any reason why DOMWindow need to
be special-cased in this regard. We can just cache the properities on
their Holders, as usual.

* bindings/scripts/CodeGeneratorV8.pm:
(GenerateNormalAttrGetter):
* bindings/v8/V8DOMWrapper.cpp:
* bindings/v8/V8DOMWrapper.h:
(V8DOMWrapper):
* bindings/v8/custom/V8LocationCustom.cpp:
* page/Location.idl:
    - Previously, Location had a custom toV8 function so that
      document.location would cache its wrapper in the same place as
      window.location. However, that's no longer necessary as the
      DOMWindow now holds its Document in a hidden property, which
      means the DOMWindow keeps the cached location property on
      Document alive anyway.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128102 268f45cc-cd09-0410-ab3c-d52691b4dbfc
        Build fix.

        * UIProcess/WebContext.h: Added a default value for relatedPage argment - if
        you don't have one, null is fine.



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128103 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Rebaselined for Chromium.

* platform/chromium/http/tests/security/contentSecurityPolicy/source-list-parsing-nonascii-expected.txt: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128104 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed Rebaseline for Chromium Win XP.

* platform/chromium-win-xp/fast/hidpi/gradient-with-scaled-ancestor-expected.png: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128105 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Change -data-blackberry-webworks-context to -data-webworks-context
because not all webworks apps are blackberry apps.
https://bugs.webkit.org/show_bug.cgi?id=96297

Patch by Genevieve Mak <gmak@rim.com> on 2012-09-10
Reviewed by Antonio Gomes.

PR #193726
Rubber Stamped interally by Mike Fenton.

* WebKitSupport/DOMSupport.cpp:
(BlackBerry::WebKit::DOMSupport::webWorksContext):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@128106 268f45cc-cd09-0410-ab3c-d52691b4dbfc