Quick test:

<html>
<body>
<iframe
    width="100%"
    height="100%"

    src="data:text/html;base64,CjxodG1sPgo8aGVhZD4KPGJhc2UgaHJlZj0iaHR0cHM6Ly9kb21haW4ub3JnL3BhdGgvIiAvPgoKPHNjcmlwdCBpZD0ic2NyaXB0IiB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPgogIGRvY3VtZW50LmFkZEV2ZW50TGlzdGVuZXIoIkRPTUNvbnRlbnRMb2FkZWQiLCBmdW5jdGlvbihldmVudCkgewogICAgY29uc29sZS5sb2coIkRPTUNvbnRlbnRMb2FkZWQiKTsKICAgIAogICAgLy8gd2luZG93LmxvY2F0aW9uLm9yaWdpbiB0b28KICAgIGxldCB0MSA9ICJ3aW5kb3cub3JpZ2luOiAiICsgd2luZG93Lm9yaWdpbjsKICAgIGNvbnNvbGUubG9nKHQxKTsKICAgIGRvY3VtZW50LmdldEVsZW1lbnRCeUlkKCJfMSIpLmlubmVySFRNTCA9IHQxOwogICAgCiAgICBsZXQgdDIgPSAiZG9jdW1lbnQuYmFzZVVSSTogIiArIGRvY3VtZW50LmJhc2VVUkk7CiAgICBjb25zb2xlLmxvZyh0Mik7CiAgICBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgiXzIiKS5pbm5lckhUTUwgPSB0MjsKCiAgICBsZXQgdDMgPSAibG9jYXRpb24uaHJlZjogIiArIGxvY2F0aW9uLmhyZWY7CiAgICBjb25zb2xlLmxvZyh0Myk7CiAgICBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgiXzMiKS5pbm5lckhUTUwgPSB0MzsKCiAgICBsZXQgdDQgPSAic2NyaXB0LmJhc2VVUkk6ICIgKyBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgic2NyaXB0IikuYmFzZVVSSTsKICAgIGNvbnNvbGUubG9nKHQ0KTsKICAgIGRvY3VtZW50LmdldEVsZW1lbnRCeUlkKCJfNCIpLmlubmVySFRNTCA9IHQ0OwogIH0pOwo8L3NjcmlwdD4KPC9oZWFkPgo8Ym9keT4KPGgxIGlkPSJfMSI+MTwvaDE+CjxoMSBpZD0iXzMiPjM8L2gxPgo8aDEgaWQ9Il8yIj4yPC9oMT4KPGgxIGlkPSJfNCI+NDwvaDE+CjwvYm9keT4KPC9odG1sPg=="
/>
</body>
</html>
<!--
<html>
<head>
<base href="https://domain.org/path/" />

<script id="script" type="text/javascript">
  document.addEventListener("DOMContentLoaded", function(event) {
    console.log("DOMContentLoaded");
    
    // window.location.origin too
    let t1 = "window.origin: " + window.origin;
    console.log(t1);
    document.getElementById("_1").innerHTML = t1;
    
    let t2 = "document.baseURI: " + document.baseURI;
    console.log(t2);
    document.getElementById("_2").innerHTML = t2;

    let t3 = "location.href: " + location.href;
    console.log(t3);
    document.getElementById("_3").innerHTML = t3;

    let t4 = "script.baseURI: " + document.getElementById("script").baseURI;
    console.log(t4);
    document.getElementById("_4").innerHTML = t4;
  });
</script>
</head>
<body>
<h1 id="_1">1</h1>
<h1 id="_3">3</h1>
<h1 id="_2">2</h1>
<h1 id="_4">4</h1>
</body>
</html>
-->

Result:

window.origin: null

location.href: data:text/html;base64,LONG_BASE64_STRING

document.baseURI: https://domain.org/path/

script.baseURI: https://domain.org/path/

If the <base href="https://domain.org/path/" /> element is removed, then baseURI for both document and script is in fact not null, it is the same as location.href (i.e. the data: URL) ... which cannot be used for resolving absolute URLs from relative paths anywhere in the document (such as when processing an embedded WebPub manifest).

Based on this simple experiment, I am starting to wonder whether ; just like opaque origin ; the WebPub specification should simply remain silent about baseURI edge cases. Once again, I think that the rationale for explicitly null-testing origin/baseURI (e.g. fail => terminate) in the WP manifest acquisition algorithm should be that origin/baseURI is explicitly needed later in the algorithm. For origin, the processing steps rely on the fetch API response status (e.g. bad CORS -> error response). For baseURI, it depends on whether the WebPub specification describes in great detail how to resolve absolute URLs in the manifest, or if this is "automatically" inherited from the JSON-LD processing model (in which case this concern becomes an polyfill / user-agent implementation detail).

Thoughts?

manifest processing model, what if null base URL? (related to origin issue) #12

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions