[meta] implement referrer attribute for navigation and embedding elements

NEW
Unassigned

Status

()

enhancement
P2
normal
5 years ago
a month ago

People

(Reporter: geekboy, Unassigned)

Tracking

(Depends on 3 bugs, Blocks 1 bug, {meta})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Like the rel=noreferrer (bug 530396) attribute for links and the referrer control offered at a document level in bug 704320 and bug 965727, we should allow web devs to set the referrer "level" for links, iframes and other embedding/navigating loads.  This would basically be a special case of the document-level referrer policy offered by CSP or <meta referrer= for an individual element.

I propose we use the same syntax as meta/CSP, but scope it to the element via a "referrer" attribute on the tag.

Comment 1

5 years ago
I'd argue that there is a use case for providing a finer-grained referrer.

Let's take an example. On Twitter, if someone tweets a link to my blog and people visit my blog via the tweet appearing on their timeline, the referrer I see is very likely the timeline page referrer (https://twitter.com/), more or less because there is no choice.
On the side of my blog, I see undifferenciated traffic from twitter.com, but have no idea which tweet specifically brought me traffic (and I'm interested, because I can engage with the people who tweeted about my blog, respond to their critics, etc.)

It'd be nice, if Twitter had a mechanism to set the tweet permalink as referrer of a link to a webpage, so I know who's been interested in my blog posts.
It looks like this bug is very close to suggesting such a mechanism.
(Reporter)

Comment 2

5 years ago
Makes sense, David.  For now (since there's no spec I know of on this feature) I'd like to match it up to another feature closer to standardization; but there's no reason we couldn't explore adding a literal/spoofed referrer as an option in the future.

Comment 3

5 years ago
This should be proposed on the WHATWG list first.

Comment 4

5 years ago
Also, if you plan on implementing: https://wiki.mozilla.org/WebAPI/ExposureGuidelines
(Reporter)

Updated

4 years ago
Assignee: sstamm → nobody
Assignee: nobody → franziskuskiefer
Depends on: 1166910

Comment 6

4 years ago
Franziskus, could you please address comment 4? Also, I'm not sure this specification is really what we want for referrer:

  https://github.com/w3c/webappsec/issues/409
Summary: implement referrer attribute for navigation and embedding elements → [meta] implement referrer attribute for navigation and embedding elements
Assignee: franziskuskiefer → nobody

Updated

10 months ago
Priority: -- → P2
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.