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

Set up explainer document in this repo with more detail for implementers #56

Closed
AramZS opened this issue Aug 24, 2023 · 6 comments
Closed
Assignees

Comments

@AramZS
Copy link
Contributor

AramZS commented Aug 24, 2023

No description provided.

@AramZS AramZS self-assigned this Aug 24, 2023
@SebastianZimmeck SebastianZimmeck added the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Oct 24, 2023
@martinthomson
Copy link
Contributor

@SebastianZimmeck, is there a specific question that the group can help you with here? Also, how much time do you expect that discussion to take? I think that we can find time for this at the meeting this week, but I need a little help with scheduling.

@SebastianZimmeck
Copy link
Member

Here is the explainer.

@martinthomson, the question is what, if anything, should be changed in the explainer to make it most helpful to implementers (e.g., publishers, browser vendors)?

I think 15 minutes would be a good amount of time to reserve.

@annevk
Copy link

annevk commented Oct 26, 2023

Some feedback:

  • The header needs to be a structured header. We should not add new non-structured headers to the web platform. (I have given this feedback a number of times.)
  • The new member of Navigator should always be present and return false when the signal is not present. Conditional members are generally not supported by Web IDL and also bad for a number of optimizations around object shapes and such.

@SebastianZimmeck SebastianZimmeck self-assigned this Oct 26, 2023
@bvandersloot-mozilla
Copy link
Contributor

The new member of Navigator should always be present and return false when the signal is not present. Conditional members are generally not supported by Web IDL and also bad for a number of optimizations around object shapes and such.

The spec defines it as always present, and false if the user hadn't expressed a do-not-sell-or-share preference at the time of navigation. The spec is reasonable imo.

@SebastianZimmeck SebastianZimmeck removed the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Oct 26, 2023
@SebastianZimmeck
Copy link
Member

As discussed in today's PrivacyCG meeting, please feel free to add your suggestions to the Explainer within the next two weeks. At that point, we will convert the Explainer format to markdown and open a PR here.

@SebastianZimmeck
Copy link
Member

The explainer is now merged into main.

The header needs to be a structured header.

This point is discussed in #6.

The spec defines it as always present, and false if the user hadn't expressed a do-not-sell-or-share preference at the time of navigation. The spec is reasonable imo.

Agreed.

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

No branches or pull requests

5 participants