16155 2012-02-28 23:28:38 +0000 Specify behavior for embedded content elements that have no browsing context 2013-02-18 12:07:16 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED WORKSFORME P2 normal --- 15653 1 dglazkov dave.null annevk bzbarsky mike public-html-admin public-html-wg-issue-tracking rafaelw robin tross public-html-bugzilla oldest_to_newest 64701 0 dglazkov 2012-02-28 23:28:38 +0000 Gecko, WebKit, and IE all implement the same behavior for IMG, AUDIO, and VIDEO elements that have no associated browsing context: they don't fetch resources, since there is not document URL to resolve against. We should add this to the spec. Perhaps a step in http://www.whatwg.org/specs/web-apps/current-work/multipage/urls.html#resolve-a-url? 64823 1 bzbarsky 2012-03-01 15:10:11 +0000 There is absolutely a document url; I don't see how there could not be. There is always a document url. I believe we should simply define all of these elements to not do any fetches while their ownerDocument has no defaultView. 64832 2 dglazkov 2012-03-01 17:23:18 +0000 (In reply to comment #1) > There is absolutely a document url; I don't see how there could not be. There > is always a document url. Maybe this just need to be fleshed out in the DOM4 spec, but as of now, the URL is not set for document when creating it using DOMImplementation.createHTMLDocument: http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-domimplementation-createhtmldocument WebKit in this case provides an empty URL (which seems in line with the spec): http://jsfiddle.net/dglazkov/9pESJ/1/ Gecko returns "about:blank". IE9 returns the main document URL. > > I believe we should simply define all of these elements to not do any fetches > while their ownerDocument has no defaultView. Sure, that sounds good too. 64838 3 bzbarsky 2012-03-01 17:40:12 +0000 > as of now, the URL is not set for document when creating it using > DOMImplementation.createHTMLDocument: There is an existing open bug on that, last I checked. 64840 4 dglazkov 2012-03-01 18:27:52 +0000 (In reply to comment #3) > > as of now, the URL is not set for document when creating it using > > DOMImplementation.createHTMLDocument: > > There is an existing open bug on that, last I checked. Nifty. I can't seem to find it :( Maybe it doesn't have an URL? ;) 64844 5 bzbarsky 2012-03-01 18:37:33 +0000 Looks like it's not longer open. https://www.w3.org/Bugs/Public/show_bug.cgi?id=13045 And DOMCore clearly says: Unless explicitly given when a document is created its encoding is utf-8, its content type is "application/xml", and its URL is "about:blank". right at http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-document-url 64845 6 dglazkov 2012-03-01 18:46:45 +0000 (In reply to comment #5) > Looks like it's not longer open. > https://www.w3.org/Bugs/Public/show_bug.cgi?id=13045 > > And DOMCore clearly says: > > Unless explicitly given when a document is created its encoding is utf-8, its > content type is "application/xml", and its URL is "about:blank". > > right at > http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-document-url Great. So the task as you formulated it is: Update the spec to define that elements do not do any fetches while their ownerDocument has no associated browsing context (that's the equivalent of defaultView being null, right?) 64847 7 bzbarsky 2012-03-01 18:56:49 +0000 It's not, actually. And neither one is equivalent to the document being the current document of the associated browsing context (if any), as far as I can tell. Which one we want depends on the behavior we want for things like prerendered documents, unloaded documents, etc. 64848 8 dglazkov 2012-03-01 19:08:37 +0000 (In reply to comment #7) > It's not, actually. > > And neither one is equivalent to the document being the current document of the > associated browsing context (if any), as far as I can tell. > > Which one we want depends on the behavior we want for things like prerendered > documents, unloaded documents, etc. Interesting. You're drawing a distinction between whether the browsing context simply isn't associated with a given document (like when it's created using DOMImplementation), or the user agent decides to not to create browsing contexts (when prerendering, data mining, etc.) for a document. Is this distinction anywhere in the spec? 64851 9 bzbarsky 2012-03-01 19:20:33 +0000 No, I'm making a distinction between documents which have no associated browsing context and documents which do have one but are not the current document in that browsing context. That distinction is most certainly in the spec. 70127 10 contributor 2012-07-18 06:57:39 +0000 This bug was cloned to create bug 17828 as part of operation convergence. 83264 11 robin 2013-02-18 12:07:16 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: none Rationale: See https://www.w3.org/Bugs/Public/show_bug.cgi?id=17828