-
Notifications
You must be signed in to change notification settings - Fork 5
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
Throw when passed a 0 for lifetimeDays #81
Comments
My vote is no. |
Would you recommend that we require that browsers abort (i.e., throw) if a value of zero is provided? The alternative is to treat the |
I prefer throwing. I see no benefit to silently treating it as a no-op. |
+1 for throwing. |
OK, now we have an issue that is not a question, but a TODO item :) Pull requests welcome. |
Why are we focused on what happens for passing 0? I thought the question was about whether we should allow impressions to be queried a long time after they are placed or should silently reduce time to live value. To which I understood @csharrison vote of "no" to be saying we shouldn't have an upper limit on the lifetime. |
@bmcase sorry there is a misunderstanding, as Martin changed the issue title. The original title of the issue was "Is 0 a valid value for lifetimeDays?" |
Thanks for clarifying @csharrison! I miss understood. In which case you were just responding with "no" zero shouldn't be a valid value. Makes sense now. |
From https://w3c.github.io/ppa/#dom-privateattributionimpressionoptions-lifetimedays:
The text was updated successfully, but these errors were encountered: