This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8918 - Are there other cases than coming from no referrer (just typing into the UA) and the noreferrer link that will result in a blank document.referrer?
Summary: Are there other cases than coming from no referrer (just typing into the UA) ...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-10 09:07 UTC by contributor
Modified: 2010-10-04 13:54 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-02-10 09:07:41 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#resource-metadata-management

Comment:
Are there other cases than coming from no referrer (just typing into the UA)
and the noreferrer link that will result in a blank document.referrer?

Posted from: 64.134.222.102
Comment 1 Ian 'Hixie' Hickson 2010-02-14 13:46:13 UTC 
There's a variety of cases, e.g. going from https: to http:, or the user agent being configured to strip Referer information, etc. Not sure how to say this in the spec without just listing all the cases I know, which would just be another incomplete list, and not much more useful (if at all).

There were some notes in the impl part that talked about some more examples, so I moved them into the author part. Hopefully that helps.


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: Partially Accepted
Change Description: see diff given below
Rationale: Tried to make it clearer.
Comment 2 contributor 2010-02-14 13:47:08 UTC 
Checked in as WHATWG revision r4740.
Check-in comment: Move around the 'impl' markers to put some more notes into the author part.
http://html5.org/tools/web-apps-tracker?from=4739&to=4740