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

Don't send translator error reports in private-browsing mode #199

Closed
dstillman opened this issue Nov 8, 2017 · 5 comments
Closed

Don't send translator error reports in private-browsing mode #199

dstillman opened this issue Nov 8, 2017 · 5 comments

Comments

@dstillman
Copy link
Member

There's existing code to prevent this for Zotero for Firefox, but we should update that for the connector.

This is deep in the translation architecture, so the best way to do this is probably to include a flag in the object passed to translate() to indicate that a report shouldn't be sent on failure.

@adomasven
Copy link
Member

adomasven commented Nov 10, 2017

This is deep in the translation architecture, so the best way to do this is probably to include a flag in the object passed to translate() to indicate that a report shouldn't be sent on failure.

There's already a pref controlling this though and at least for the client that's the only way of control. I'm happy to just add the handling code for extensions there. Thoughts?

@dstillman
Copy link
Member Author

That pref isn't really relevant. This is specific to private browsing, and is just a reimplementation of the existing protection we've always had in Zotero for Firefox. Extensions shouldn't upload URLs from private browsing with default settings.

What do you mean by "at least for the client that's the only way of control"? This is just for the connector.

@adomasven
Copy link
Member

This is a question regarding adding a flag to be passed to translate(). So we'd have translate.reportTranslationFailures flag that had been passed in via translate() and the pref, which is confusing. I propose to just add the incognito check there in translate.js.

@dstillman
Copy link
Member Author

Ah, I see what you mean. I was assuming we might not have easy access to the incognito check at the point of the existing code. If we do, that's fine. If not, I figured we could have a skipFailureReporting or something at the point of the translate() call, and that would disable reporting even if the pref was on.

@adomasven
Copy link
Member

Closed with 0192bda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants