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

Update and publish referrer policy feature #1299

Merged
merged 2 commits into from
Jul 12, 2024

Conversation

foolip
Copy link
Collaborator

@foolip foolip commented Jul 2, 2024

Trim the BCD keys to just HTTP header and HTML attributes. Pin the
status to the same but ignoring the reflectd API since that's not key to
using this.

Note that support in <script> came a bit later but the Baseline year is
2020 regardless, so include it in compute_from.

Fetch and SVG integration is excluded, as it's not part of the feature
description.

All the entries for specific values like "no-referrer-when-downgrade"
are also removed since the data for that looks messy and would need
detailed review to have confidence in it.

@github-actions github-actions bot added the feature definition Creating or defining new features or groups of features. label Jul 2, 2024
features/referrer-policy.yml Outdated Show resolved Hide resolved
Trim the BCD keys to just HTTP header and HTML attributes. Pin the
status to the same but ignoring the reflectd API since that's not key to
using this.

Note that support in <script> came a bit later but the Baseline year is
2020 regardless, so include it in compute_from.

Fetch and SVG integration is excluded, as it's not part of the feature
description.

All the entries for specific values like "no-referrer-when-downgrade"
are also removed since the data for that looks messy and would need
detailed review to have confidence in it.
@ddbeck
Copy link
Collaborator

ddbeck commented Jul 8, 2024

I noticed that, but thought it's strange to make the default part of the feature. After all, the default is what you get when you don't use the feature (header or attributes) at all. On the other hand, as a matter of spec and implementation, the default is part of the feature.

I'll add some comment or TODO about this.

FWIW, I agree that it's a bit weird. I think the TODO might be to ask caniuse to make the change. Aligning with caniuse is pretty important, I think, since that's often how developers know what a feature is, in terms of compat.

baseline_low_date: 2021-09-20
baseline_high_date: 2024-03-20
support:
chrome: "85"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I've sent Fyrd/caniuse#7108.

@foolip foolip merged commit 72638bd into web-platform-dx:main Jul 12, 2024
3 checks passed
@foolip foolip deleted the referrer-policy branch July 12, 2024 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature definition Creating or defining new features or groups of features.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants