26152 2014-06-20 10:40:01 +0000 Would it not be better to define origin as identifier, tuple, or, alias? That alias is actually a link to another origin is not super clear this way. 2014-09-18 20:39:24 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#origin-0 P3 normal Unsorted 26221 1 contributor ian annevk ian mike w3c contributor oldest_to_newest 108107 0 contributor 2014-06-20 10:40:01 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html Multipage: http://www.whatwg.org/C#origin-0 Complete: http://www.whatwg.org/c#origin-0 Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Would it not be better to define origin as identifier, tuple, or, alias? That alias is actually a link to another origin is not super clear this way. Posted from: 77.57.114.66 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0 108108 1 annevk 2014-06-20 10:42:47 +0000 Also what do you think about putting the main origin definition in Fetch, as well as serializing it, and how to obtain it for URLs (including blob URLs)? I already obsolete parts of the original RFC as the Origin header needed new ABNF, might as well complete it and make HTML a little leaner. 108140 2 ian 2014-06-20 21:15:14 +0000 "Origin" should be defined wherever document.domain is defined, IMHO, because so much of the complexity around origins comes from that. document.domain should be defined wherever we define the Window/Location cross-origin stuff. That should be defined wherever we define browsing contexts; those should probably be defined where we define the navigate algorithm; that should probably be in the same spec as "The End" of parsing, and _that_ should be in the same spec as the HTML parser. How do you feel about owning the HTML parser? :-) 108213 3 annevk 2014-06-23 11:10:30 +0000 That seems clear. Any reason we need the "Web Origin Concept" specification then? Is that mostly to get an origin out of a URL? It seems the URL Standard ought to cover that. Could you fix comment 0 then? Defining "alias" as a possible value. 108245 4 ian 2014-06-23 20:36:31 +0000 Yeah, that's not a bad idea. I'll look into it. I'm not sure about the Web Origin Concept spec. I seem to recall we had a good reason to do it at the time, but it seems to have somewhat become moot. cc abarth. 108423 5 annevk 2014-06-27 13:18:28 +0000 URL now defines origin for URLs: http://url.spec.whatwg.org/#origin 111765 6 contributor 2014-09-18 20:37:54 +0000 Checked in as WHATWG revision r8787. Check-in comment: Move the reference for URL origin from Web Origin to URL. https://html5.org/tools/web-apps-tracker?from=8786&to=8787 111766 7 ian 2014-09-18 20:39:22 +0000 Comment 5 confused me. It was probably meant for bug 26221. I'll mark that as a dupe of this bug. The patch above also fixes the alias thing. 111768 8 ian 2014-09-18 20:39:24 +0000 *** Bug 26221 has been marked as a duplicate of this bug. ***