From 00769464e80149368672b894b50881134da4602f Mon Sep 17 00:00:00 2001 From: Mike West Date: Tue, 13 Sep 2016 11:20:33 +0200 Subject: [PATCH] Treat 'data:' documents as unique, opaque origins (#1756) This patch changes the handling of 'data:' URLs to which user agents navigate. Rather than inheriting the origin of the settings object responsible for the navigation, they will be treated as unique, opaque origins. This aligns the spec with the behavior found in Chrome, Safari, Opera, and Edge. Closes whatwg/html#1753. --- source | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/source b/source index 0c7f2ff578a..358f773f79d 100644 --- a/source +++ b/source @@ -79507,6 +79507,9 @@ callback FrameRequestCallback = void (DOMHighResTimeStampIf the Document's active sandboxing flag set has its sandboxed origin browsing context flag set +
If the Document was generated from a data: URL
+

A unique opaque origin assigned when the Document is created.

@@ -79534,10 +79537,6 @@ callback FrameRequestCallback = void (DOMHighResTimeStampIf the Document is a non-initial "about:blank" document -
If the Document was generated from a data: URL found in another Document or in a - script
-

The origin of the incumbent settings object when the navigate algorithm was invoked, or, if no script was involved, the origin of the node @@ -79560,10 +79559,9 @@ callback FrameRequestCallback = void (DOMHighResTimeStamp's node document.

-
If the Document was obtained in some other manner (e.g. a data: URL typed in by the user or that was returned as the - location of a redirect, a Document created using the createDocument() API, etc)
+
If the Document was obtained in some other manner (e.g. a Document + created using the createDocument() + API, etc)

The default behavior as defined in the WHATWG DOM standard applies. .