- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 03 May 2011 18:11:28 +0200
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: public-iri@w3.org
On 03.05.2011 17:58, Boris Zbarsky wrote:
> On 5/3/11 4:50 AM, Julian Reschke wrote:
>>> <iframe id=foo src="about://blank" onload="test()"></iframe>
>>> <script>
>>> var doc = document.getElementById("foo").contentDocument;
>>> var anchor = doc.createElement("a");
>>> anchor.setAttribute("href", "foo.html")
>>> doc.body.appendChild(anchor);
>>> alert(anchor.href);
>>> </script>
>>> ...
>>
>> FF4: resolves against the document's URI (not about://blank)
>
> In general, for iframes containing about:blank documents we use the
> "originating" uri of the about:blank as the base URI. We found that this
> was needed for web compat in at least some cases.
Ack, and thanks for the explanation.
So many of these edge cases really aren't about URI/IRI parsing
resolving, but about HTML, and *selecting* the base URI/IRI. We
shouldn't confuse those questions.
Best regards, Julian
Received on Tuesday, 3 May 2011 16:12:13 UTC