Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

Change 'save' button to 'upload' button #4963

Merged

Conversation

jaredhirsch
Copy link
Member

I think we were wrong to use 'Save' to mean 'Upload', and I don't recall why we went with it in the first place. It could seem like we're desperate to trick people into uploading shots. Let's not give that impression.

screen shot 2018-09-26 at 1 10 48 pm

@@ -6,6 +6,7 @@ contextMenuLabel = Take a Screenshot
myShotsLink = My Shots
screenshotInstructions = Drag or click on the page to select a region. Press ESC to cancel.
saveScreenshotSelectedArea = Save
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this string is unused, it should be removed from the file.

@johngruen
Copy link
Contributor

johngruen commented Sep 27, 2018

Why don't we ditch the string altogether and just use a title like on the other buttons?

@jaredhirsch
Copy link
Member Author

Why don't we ditch the string altogether and just use a title like on the other buttons?

SGTM 👍

@johngruen
Copy link
Contributor

@6a68 i made a PR into your branch to remove the string from the upload button:

jaredhirsch#8

@evilpie
Copy link

evilpie commented Oct 5, 2018

I am not a big fan of removing the text, have we thought about going to opposite way, i.e adding "Save" etc. ? Even the titles on hover could be more descriptive, like "Save file to disk", "Upload to screenshots.firefox.com"

@johngruen
Copy link
Contributor

@evilpie like the idea of having longer tooltips. I'm less enthusiastic about adding more text to buttons b/c localization will make the widths weird. I'll check in with our content strategy person and update strings.

@jaredhirsch
Copy link
Member Author

@johngruen Hmm. I fear that removing the text will take us from 'misleading button label' to 'inscrutable button label':

screen shot 2018-10-10 at 1 28 31 pm

@johngruen
Copy link
Contributor

@6a68 not an hill i want to die on. We can keep the Upload text for a release and look at metrics to determine effects... R+, but can you change two colors in the sass variables file.

$link-blue: #0a84ff;
$active-blue: #45a1ff;

Copy link
Contributor

@johngruen johngruen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a comment about changing to variable color values, but otherwise good to go

@schuetzm
Copy link

Please also change the download button to "save", with an appropriate icon. Nothing is being downloaded here, it's a purely local operation (or should be, at least).

@muxator
Copy link

muxator commented Oct 17, 2018

Please also change the download button to "save"

Agreed.

@jaredhirsch
Copy link
Member Author

@johngruen Hmm. We could A/B test this label change, since it will change the core flow of the product. Might actually be a good exercise to get us prepared for the growth focus in Q1 of next year. How's that grab you?

@jaredhirsch
Copy link
Member Author

@schuetzm Thanks for the feedback, but I think it's actually much worse to change a button label to a different button, than it is to change the label to a new word. If you are used to the Screenshots convention that 'save' means 'upload', you are going to be unpleasantly surprised to discover 'save' suddenly means 'download'.

@Deledrius
Copy link

If you are used to the Screenshots convention that 'save' means 'upload', you are going to be unpleasantly surprised to discover 'save' suddenly means 'download'.

That's a reasonable concern, and I generally agree, but not fixing the mistake because the mistake was made is a circular justification. Both of these buttons are misleading (and factually incorrect). Leaving one wrong because it's been wrong just prolongs the problem. Will it be acceptable to fix this later, after it's been mislabeled even longer? If anything, user confusion is precisely the reason this should be rectified as soon as possible (in fact, it would have avoided this new concern altogether had it been fixed when the privacy issue was first reported over a year ago).

More directly: leaving the save button as "Download" generates confusion over the initial disposition of the image. If I can both Upload and Download the image, where is it? Is it being produced on Mozilla's server? Is it produced locally? A user can't be sure, because the language implies both and neither simultaneously.

There is a standard convention for this sort of interface: local data may be saved from memory onto disk, or they may be uploaded to a remote location. The improved UI, even with this commit which addresses the privacy violation implications resulting from the mislabeled button, still doesn't adhere to this convention.

I suppose that's a problem for a different PR, however. It's just a bit frustrating to see part of this poor UX persisting.

@schuetzm
Copy link

@6a68 I strongly disagree with this; @Deledrius has explained the reasons very nicely. And I frankly find it quite disconcerting that it is necessary to argue about basic things like this. If making the additional changes takes too much time, then by all means just merge the PR now as-is, so that at least the worst privacy-related problem is fixed. But this mustn't be a justification not to tackle the other glaring problem immediately afterwards.

@muxator
Copy link

muxator commented Oct 21, 2018

Just for info: I am on Firefox 63 (Ubuntu 18.10), but this PR did not make it.
Maybe in 6 weeks for Firefox 64 we'll have it!
screenshot at 2018-10-21 16-32-38

@jaredhirsch jaredhirsch merged commit 1ab37a5 into mozilla-services:master Oct 30, 2018
@muxator
Copy link

muxator commented Mar 21, 2019

Quick update: at least the official Windows x64 Firefox 66 package seems to miss this modification.
The Upload button still reads Save.

Cattura

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants