freejoy — 2012-09-24T17:04:22-04:00 — #1
Here's what I mean:
Click from page "A" (i.e. regular product page)
Go to page "B" (i.e. account Login) NOTE: Back button works to go back to product page at this point,
Go to page "C" (i.e. start an account, because they didn't login because they don't have an account yet)
Then if they decide not to start an account and click back they go from start an account page "C" back to "B" okay. But if they click the back button on Account Login page "B" they go back to page "C" agian. Back and forth between "B" and "C".
I need them to be able to progressively back up to the page "A" they were at.
<a href="#" onclick="history.go(-1);return false;" class="back-link">
stevie_d — 2012-09-24T17:38:00-04:00 — #2
freejoy — 2012-09-24T18:07:43-04:00 — #3
Yeah I know. But it kind of looks professional
freejoy — 2012-09-24T20:22:30-04:00 — #4
I thought of some more reasons.
It gives the customer a feeling of security that he is not being trapped when he sees the back button.
It enhances user experience because they don't have to move their mouse as far. haha
ralphm — 2012-09-24T21:36:47-04:00 — #5
felgall — 2012-09-24T22:10:48-04:00 — #6
freejoy — 2012-09-24T22:48:21-04:00 — #7
ralphm — 2012-09-25T00:03:14-04:00 — #8
O dear, that's really bad practice. JS should be an extra layer to add functionality. The content / basic functionality should not depend on it.
stevie_d — 2012-09-25T03:16:13-04:00 — #9
Not when it doesn't work, it doesn't!
freejoy — 2012-09-25T14:57:23-04:00 — #10
freejoy — 2012-09-25T15:01:35-04:00 — #11
Yeah, it not professional if it doesn't work. I like the cancel button idea, but still one would want to be redirected back to the page they were viewing. I'm thinking some kind of php script might be better.
ralphm — 2012-09-25T19:54:37-04:00 — #12
It's usually better to use a server-side language like PHP, because it doesn't depend on what your user's setting are to work.