Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One attempt at figuring out the referrer source issue #13

Closed
wants to merge 2 commits into from

Conversation

hallvors
Copy link

@hallvors hallvors commented Nov 9, 2013

  1. "script's referrer source" is no longer defined in HTML it seems (certainly not in the location it was according to the xrefs). I assume "API referrer source" is the equivalent concept (although I have not found any related discussion and it's not at all clear to me why the spec distinguishes between script's responsible document and its API referrer source as it does for example in step 4 here: http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#processing-model-7

  2. In fact referrer source should always be referencing a Document when xhr.send() runs - by the algorithms over in the Worker spec and those in XHR itself - but the "API referrer source" definition says it can be a URL too, so it seems prudent to take that into account and put in ".. if it's a document, otherwise..".

1) "script's referrer source" is no longer defined in HTML it seems (certainly not in the location it was according to the xrefs). I assume "API referrer source" is the equivalent concept (although I have not found any related discussion and it's not at all clear to me why the spec distinguishes between script's responsible document and its API referrer source as it does for example in step 4 here: http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#processing-model-7

2) In fact referrer source should always be referencing a Document when xhr.send() runs - by the algorithms over in the Worker spec and those in XHR itself - but the "API referrer source" definition says it can be a URL too, so it seems prudent to take that into account and put in ".. if it's a document, otherwise..".
@annevk
Copy link
Member

annevk commented Nov 11, 2013

This is not correct. You should have an xref for URL and such. Once the issues in the bug are sorted I'll make this edit.

Also, we shouldn't have things like "prudent". We need to actually know.

@annevk annevk closed this Nov 11, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants