Warning about replacing a project with file>upload... is not explicit enough
See original GitHub issueExpected Behavior
When choosing File>Load from your computer
it should give a warning that makes it clear that you are deleting the current project.
Actual Behavior
The current error message has not made that clear to some users. The current message says: “Replace contents of the current project?”
One person said "And I clicked yes, because I had just saved the [project name] project so I assumed it was safe to do so. "
We should likely explicitly say that by “replace” we mean “delete.” It could say “Replace the contents of the current project? This will delete the current project.”
Steps to Reproduce
Create a new project
Choose File>Load from your computer
Choose a project from your computer
Note: the alert appears. It can be interpretable as not meaning you’re deleting your old project.
Operating System and Browser
Mac Chrome
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 by maintainers)
Top GitHub Comments
Just tossing out an idea, haven’t thought too deeply about so there may be other issues by this approach.
We have always had this tension of how understandable is this action as it feels it’s described as a single action, but it does two things: both uploading and replacing contents. Of course, there is good reason that “Upload” replaces the contents of a project, for example in the case that someone has downloaded a project, made changes offline, and wants to re-upload the project of a previously shared project so it retains all community data related to the project (e.g. loves, favs, comments, studios…).
Maybe, we should instead have decouple these and have two different options in the file menu. One could imagine it being something like: “Upload to new project…”, “Upload and replace…”, and “Download project…”
Exact language should be taken with a grain of salt, using this the language above for sake of discussion.
This might help with being able to reenforce that these are two different actions, instead of trying to describe one without the context of the other. We could still pop a modal / alert to give more context, but having both represented might help clarify they are different. It allows for the more nuanced use case of “upload and replace” to still exist, but as distinguished from what some people expect which is to “upload to new project” (or upload and not replace contents).
I labeled this High impact, high severity. Making the text change Bryce suggested would be really fast and seems to me like an improvement.