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

Fixes #255 - Make it clear UA-CH doesn't want _more_ entropy out of browsers #265

Merged
merged 4 commits into from
Sep 24, 2021

Conversation

miketaylr
Copy link
Collaborator

@miketaylr miketaylr commented Sep 23, 2021

PTAL @yoavweiss @martinthomson


💥 Error: 400 Bad Request 💥

PR Preview failed to build. (Last tried on Sep 24, 2021, 2:16 PM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 CSS Spec Preprocessor - CSS Spec Preprocessor is the web service used to build Bikeshed specs.

🔗 Related URL

Error running preprocessor, returned code: 2.
FATAL ERROR: Couldn't load MDN Spec Links data for this spec.
Expecting value: line 1 column 1 (char 0)
 ✘  Did not generate, due to fatal errors

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

@miketaylr miketaylr requested a review from yoavweiss September 23, 2021 18:18
Copy link
Collaborator

@yoavweiss yoavweiss left a comment

Choose a reason for hiding this comment

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

LGTM

index.bs Outdated Show resolved Hide resolved
Comment on lines +929 to +932
However, it will still be possible for some, or all, hints to be requested and used for
[=active fingerprinting=] purposes by first or delegated third parties. As noted in [[#access]],
[=user agents=] should consider policies to restrict or reduce access to parties that are known to
<a lt="active fingerprinting">actively fingerprint</a> their users.

Choose a reason for hiding this comment

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

I'm also seeing a need to strengthen the access restrictions section cited here. It doesn't concretely say what might happen if a browser decides to restrict access.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks, agree it can be improved. I've filed #266 to tackle this.

@miketaylr miketaylr merged commit 6f090a7 into WICG:main Sep 24, 2021
@miketaylr miketaylr deleted the issues/255/1 branch September 24, 2021 14:23
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.

3 participants