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

Adjust eligibility-header validation with respect to fetch options #1209

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

apasel422
Copy link
Collaborator

@apasel422 apasel422 commented Mar 21, 2024

After #757, user code no longer manually sets the
Attribution-Reporting-Eligible header, but the validator was never updated to properly reflect that.

We remove the warning about navigation-source (since the header is effectively always browser-set) and add errors corresponding to nonexistent key combinations (navigation-source always occurs in isolation).

After WICG#757, user code no longer manually sets the
Attribution-Reporting-Eligible header, but the validator was never
updated to properly reflect that.

We remove the warning about navigation-source (since the header is
effectively always browser-set) and add errors corresponding to
nonexistent key combinations (navigation-source always occurs in
isolation).
@apasel422 apasel422 marked this pull request as ready for review March 21, 2024 12:50
@apasel422 apasel422 merged commit efa742a into WICG:main Mar 21, 2024
2 checks passed
@apasel422 apasel422 deleted the validate branch March 21, 2024 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants