display warning when user navigates back in web browser

[JAvRZ]

All fields are still active, but changing the values in some fields (age, test scores) do not seem to affect the visualisations or the tables. It seems like the ocpu/normcomp part isn't run the second time, because other things, unrelated to normcomp like the names of the participant, can be changed and will show up differently the second time one goes to the visualisation.

[mkuzak]

Currently there is no previous from the visualization. Should there be one?

[JAvRZ]

If there is no previous button, I think it is inevitable that people are going to try the back button in the browser (because of iterative analyses, discovered typos in test scores, interest in other patients). So if there is no Previous button, I think people wouldn't mind too much because they can use the Backbutton, but I'm worried of unexpected behaviors when they do.

[mkuzak]

What we need is to define exactly the behaviour of going back and forth, what is being kept, what is being refreshed etc.

[JAvRZ]

I think people like that things are kept, so that you can look at a extremely aberrant test result, think, hold on, that's not right, go back, see that you typed in 66 instead of 6, remove one 6, and go back to the results. If everything is refreshed once more, you can only retry from a blank slate (and have to look up the 6 from scratch). I btw find myself pressing the previous button in the table under the plots (that's a different "Previous", I know, but my reptile brain does not).

[mkuzak]

As discussed recently, we will alert users when they usenext and back/prvious in the browser and in the page. They should not expect any data to be kept in place.
For listening on browser navigation:

window.onbeforeunload = function() {
    return "Leaving this page will reset the wizard";
};

after this stack overflow thread

[mkuzak]

the solution with "onbeforeunload" does not work, according to docs it can be ignored by the browser

[jvdzwaan]

I came across this solution using angular: http://stackoverflow.com/questions/15813850/how-to-detect-browser-back-button-click-event-using-angular

However, not sure this always works (and how to check whether it does)

[mkuzak]

I'll give it a shot.