- This topic is empty.
-
AuthorPosts
-
July 15, 2014 at 8:33 am #175466
Coen
ParticipantIn order to force users to properly safe their inputs we ‘d like to prevent them to use any browser navi (forward, backward, refresh and home).
What is the best way to do this, cross browser proof???July 15, 2014 at 8:59 am #175468Paulie_D
MemberWhat is the best way to do this.
The answer is DON’T.
Frankly, I cannot think of ANY reason to do this. If I found that my browser buttons did not work on your site I would run away as fast as I could, never come back and tell my friends to avoid it.
I assume you mean ‘save their input details` or something like that.
I think you are trying to solve a specific problem in completely the wrong way.
July 15, 2014 at 9:16 am #175471nixnerd
ParticipantYeah, I gotta second @Paulie_D. I’m ALL FOR making sites do things they’re “not supposed to do.” But… when you infringe upon the user’s freedom to leave your site, that goes beyond avant garde and moves into the territory of downright malicious.
The only way to do this would be to find and use an exploit for all the browsers you want to target. Don’t do it. Don’t even try.
July 15, 2014 at 9:17 am #175472nixnerd
ParticipantYou can check if a user is trying to leave a page without saving their information
Codepen does this and it’s perfectly fine. That is an acceptable tactic.
July 15, 2014 at 3:09 pm #175503Coen
ParticipantThanks for your suggestions above. I will look into them. I would like to stress there are no malicious intentions here. Let me go into more detail. We have an application by which users can book reservations online. We abandoned the safe button as a design principle because we don’t want to bother our users with superfluous clicks. Just checking a checkbox should be enough to write the reservation into our database. All fine so far. But some users use their browser back button after making a reservation and respond positively to the browser message “Do you want to reload the previous page?” and then later blame us for our system to fail in storing their reservation. Our only defense is to explain NOT to use the browser back button again but use our in-system back button instead. To get rid off this problem for once and for ever we would like to shut off browser navigation. I feel The Doc’s solution (or Codepen?) could be an improvement. But even better would be to turn the browser navi buttons into ghosted…. Suggestions are welcomed. I will keep you posted.
July 15, 2014 at 4:05 pm #175505shaneisme
ParticipantBasically you can’t do it, and you shouldn’t.
Your issue is a problem with design, not the browser.
July 16, 2014 at 1:54 am #175518Paulie_D
MemberOur only defense is to explain NOT to use the browser back button again but use our in-system back button instead.
And what’s wrong with that?
I see this many times on many sites and I do a LOT of online hotel and flight bookings as another aspect of my job.
July 16, 2014 at 4:04 am #175535Coen
ParticipantFor now we’ll settle for the quick and easy possibility 2 and in time we’ll apply possibility 1.
Thanks a lot to everybody four your advice. Great!
-
AuthorPosts
- The forum ‘Other’ is closed to new topics and replies.