Firefox Screenshots team regret why they labeled ‘Upload’ button in Screenshots UI as ‘Save’ in the first place as it is misleading, but still, the changes made to correct the issue has not yet landed into Firefox browser, we don’t know the reason for that.
Screenshots feature built-into Firefox browser and available in the page actions menu and page right-click menu, when selected, shows ‘Save’ button along with cancel, copy to clipboard and Download buttons in UI when you capture some portion on the screen. Clicking save button will upload the image to screenshots.firefox server and a link will open and displayed in a new tab with a toolbar to let the user share screenshot URL, edit, copy to clipboard, download the image to his computer.
The saving button is something we use or associate when storing something locally to a disk where here the button is doing the uploading. The button should actually have been labeled as ‘Upload’, but not save. This has been acknowledged by Screenshots team and a bug has been created on the feature GitHub page. You can also see some concerns raised by users on Reddit about this here and here.
In the bug with name ” change save to upload button, Product engineer @Mozilla, Jared Hirsch said “I think we were wrong to use ‘Save’ to mean ‘Upload’, and I don’t recall why we went within the first place. It could seem like we’re desperate to trick people into uploading shots. Let’s not give that impression”.
Here is how screenshots UI looks like after changing Save button to Upload.
FYI, the issue has been fixed on October 31, 2018 by Screenshots team and fixes haven’t been ported to Firefox 64, that was released on December 11, 2018, there is no official information if the changes to Firefox Screenshots save string will land and ship with Firefox 65, which will release on January 29. 2019.
Update: When we contacted Jared on which Firefox release version will get the fix, he said Firefox 66 or 67.
Looking like 67 at this point. Maybe 66.
— jared hirsch (@6a68) January 16, 2019
What’s your take on this? As this is a small issue, is it right for Mozilla to ignore fixing this in Firefox?