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
Review request for Push API #184
Comments
Please consider carefully that user agents effectively requiring a single push service may introduce concerns related to privacy and security, as well as internationalisation given the realistic scenario that a "standard" service may be unavailable regionally. The asserted design trade-off is against efficiency for power consumption. It would be helpful to understand whether the TAG supports this sort of design, and what should be taken into account in determining the trade-off between power consumption and user privacy and security. |
Comments from f2f: no explainer... |
Thanks for looking at this. Do you think comments by 31st July might be possible? |
@LJWatson we are looking at this now. |
I tend to pick a lot of nits and couldn't find any to pick. |
Overall we have no substantive feedback, and the API looks great. On the push service relationship with the browser:
|
From @LJWatson:
I'm requesting a TAG review of:
Further details (optional):
We'd prefer the TAG provide feedback as (please select one):
The text was updated successfully, but these errors were encountered: