BAD CHROME, BAD BAD CHROME

My latest experience took place a couple of minutes ago, and while still affected, I would like to share it with you. There is one big, really big rule with regard to user-centered design: "Never loose the user's work". This is extremely annoying for the user and usually results in a negative attitude towards the product that allowed it to happen. One might think this is only applicable to a mobile usage scenario, where content takes much more time to create, compared to the desktop one. This is true, but nevertheless content should never be lost, under any circumstances. Both my experiences are related to facebook but while one was solely their issue and has been recently fixed, the other is an issue of my desktop browser and is applicable to other websites as well. A few months ago I was extremely discouraged by the facebook Android app, which lost my post content a few times within a month. Imagine the following scenario: you write a status update that is 200 symbols long and takes quite some time on the touch screen. Then when you post it your phone suddenly realizes that the internet connection is very bad. You get an OS message informing you about your wonky connection and the facebook app refreshes sending your post to a black hole. This gave me shivers every time I wanted to do a status update over my phone. I started to copy my whole post upon completion being afraid that it might get lost and when I occasionally forgot to do so guess what happened – my internet connection was bad and I was shaking with anger again. A month or so ago the app was updated and I was extremely satisfied to find out that they dealt with the issue, allowing you to send your status update again through a notification, received when the initial update failed. That update really made my day. However, my latest experience showed that this is not valid for the web. There the browser, not the website should be responsible for not losing your content, because we don't want this to happen anywhere. Here is what happened earlier. I was writing a really long and emotional status update but at some point made a spelling error, pressed the backspace on my keyboard and it took me to the previous site I was at. I literally froze for while. I clicked the browser forward button with hope, but knew that it all was inevitably gone. As a result I am never going to be able to write the very same text again or give it the same emotional charge, and I blame Chrome for that. Of course one should never be critical unless he has a solution to the problem and here is mine. I imagine a perfect world, in which when Chrome decided that my intention was to go back, being aware that I created some content on my current view, it stored it to some clipboard. It also gave me a visual hint about this process and only then sent me back to my previous website. My content would be there if Chrome misunderstood my intention and I would be able to continue my update if I wanted. P.S. One big excuse to all my facebook friends, who will not be able to read my post but Chrome is the one to blame and next time you decide to create a long post for the web, do it in locally and paste it to your browser in the end as I am doing now.