-
Notifications
You must be signed in to change notification settings - Fork 128
Create "download only" mode #3574
Comments
@clouserw why does this need product? We've already discussed this in our standup. |
@johngruen only if there is anything around when to show the label. Eg. number 2 up there -- do we want to warn about 3rd party cookies? Sounds like needs:ux is most appropriate now. |
Two quick proposals here: Option A shows a simple message about "Download-only mode" and users can click on the info button to open the tooltip and learn more about what download-only mode is. Option B shows the whole message in a block placing at the bottom left corner. This is a temporary copy and it should be modified by copywriters to help users better understand the situation. |
@youwenliang lets go with option A with the caveat that i think that tooltip should just show up on hover, so we can ditch the [x] control |
@youwenliang can you provide a measurement spec for option A and then unassign yourself? |
Here's the measurement: https://mozilla.github.io/testpilot-assets/Firefox_Screenshots/FFSS-3574/ |
* Fix #2818, use the private browsing download manager in private browsing mode Thanks to https://bugzil.la/1362448, webextensions will use the correct download manager, depending on the `incognito` state of the window. * Fix #3274, Enable Screenshots in private browsing mode Leave the l10n string in place, in case this decision is reversed * Partial fix for #3574, create download only mode for private browsing
There are a couple situations where we want to let the user use Screenshots and download their shot, but not allow them to upload the shot.
The three cases we are specifically thinking about:
To do this bug, potentially only one of these cases might be handled, and we can do a follow-on for the other cases.
The second two are based on Firefox preferences, and we would have to read these preferences in bootstrap.js. This would be sent to the WebExtension in the same manner (or at the same time) as the Telemetry/FHR preference.
The text was updated successfully, but these errors were encountered: