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
Selectively exposing the API could be a fingerprinting vector #95
Comments
Another case in point is that even The current text could be misinterpreted that the API shouldn't be exposed if the user has set a preference to not show badges (as "it never displays badges"). |
My interpretation of that line is different - it sounds to me like User Agents in which don't support application badges at all (i.e. Firefox Desktop, Chrome Android) should not expose the API, rather than saying the API shouldn't be present if it isn't going to do anything. At least, that's how I interpreted it when I was implementing it in Chromium. Could definitely be clearer though :) I think it was intended as feature detection for |
Ok, let's stick with the current wording. |
The spec states:
This implies that the API is only ever revealed for installed web applications. That, in turn, reveals if the user has installed the web application*.
It might be better to consider always exposing this API and making it a no-op. Chrome already behaves likes this, for instance.
*there are other ways that a third-party could figure out if a web application is installed (e.g., through checking the "display-mode" media feature, thought that doesn't 100% assure the application is "installed"). However, this exacerbates the problem.
The text was updated successfully, but these errors were encountered: