995752 - Suggestion - Alert before creating a new project in webmaker

Status: RESOLVED WONTFIX

(Webmaker Graveyard :: General, defect)

Description

[iamjayakumars]

Most of the Issues in SUMO(Support Mozilla) about WebMaker is Unable to Save the Project.

The Issue may be arise because of the following things
*Cookie Issue or corrupted cookies
*Session Expired of already Loged In Persona


So in SUMO we asked them to clear the cookies, Create new session or refresh the page. so the project them done everything they are loosing.

Sometimes the Firefox crash and they loose all the project they worked on. 

So its better to show an "ALERT" when they click the New Project in Thimble/Popcorn

Comment 1

[Pomax]

This should already be protected in Thimble (page navigation with changed content will ask for a navigation confirmation) but I'm not sure about popcorn. Asking thecount to weigh in on this.

Comment 2

[Scott [:thecount] Downe]

Yes, popcorn has a warning if you try to leave with unsaved changes.

Clicking new from inside the menu opens a new tab, with the old tab and project left untouched.

Comment 3

[iamjayakumars]

I'm not talking about after the thimble project started. 

I'm talking about before. I'll provide some sample Support Questions for that.

Comment 4

[Pomax]

can you add more details on what this bug is about? I do not understand the intial description; if you have some Steps To Reproduce that we can walk through, with expectations vs. what really happens, that would be very helpful, otherwise we'll have to close this bug as having not enough information to identify and then fix the problem with.

Comment 5

[iamjayakumars]

When we open the "https://thimble.webmaker.org/" or "https://popcorn.webmaker.org/" page, we can start working on the new project, whether we signed in or not, doesn't matter. 

When they try to save their project, getting error because of cookies, webpage issue, crash etc.. That time user looses everything and posting in the forum(SUMO), about retrieving their project.

So, I think its better to create a JS alert to show "Login to start your project".

Comment 6

[Pomax]

it should not be the case that you need to be logged in before you start, so if people are losing their work at login time, we need to address those instead. Do you have actual examples of how things can go wrong here? i.e. I haven't seen a browser crash in many years, and cookies shouldn't get in the way of a login failure, since the persona login should simply update that cookie.

We could do a "project cache" for sessions that haven't logged in yet, so that if someone logs in, that data is reloaded (from localStorage perhaps). Thecount: does Popcorn have something like this already?

Comment 7

[Scott [:thecount] Downe]

We do a backup save the project to local storage every so often, and mark the backup as needed if there is a js error or failed save, on refresh it asks if they want to load the backup, so they can attempt another save. It however does not backup if the login failed, forcing the user to close the project and lose their work. It's probably a very painful experience to willingly give up those changes knowing there is nothing that can be done.

That's the current auto backup.

I would say the priority should be to track down why login fails.

Secondary solution would be to backup the project if login failed, but that might get confusing because login can fail because of a simple typo in the password, causing an unexpected backup to be loaded, potentially being loaded on top of the intended project.

Comment 8

[Pomax]

closing as the problems underlying this effect should be fixed instead.