Do you know what they are coding in? PHP?, ASP?
The language may offer a specific solution, but the storing in a
session might work, but as said, some situations don't pass the HTTP-
REFERRER.
But ultimately, in a WS-friendly world, is there no way to help
convince them to follow this
That's not *fixing* the back button and is a consequence of the AJAX
refresh JS instead. It is the JS that needs to be fixed
joe
On Jan 19 2008, at 17:43, Michael MD wrote:
Are we agreed that the back button *should* take one to the
previous page?
yep .. speaking of which...
Is there
Are we agreed that the back button *should* take one to the previous page?
yep .. speaking of which...
Is there a good way to fix up back button behaviour (so it behaves as
expected) on pages that do stuff like loading data by using javascript in
hidden iframes?
way out of my league
On Jan 19, 2008, at 12:43 PM, Michael MD wrote:
Are we agreed that the back button *should* take one to the
previous page?
yep .. speaking of which...
Is there a good way to fix up back button behaviour (so it behaves as
expected) on pages that do stuff like loading data
sorry about mylast response, i was having an email blitz with my
brother whose name is mike..
--ron
On Jan 19, 2008, at 12:43 PM, Michael MD wrote:
Are we agreed that the back button *should* take one to the
previous page?
yep .. speaking of which...
Is there a good way to fix up back
Hi list
This is starting to move off topic, if not already there. Being more a
question of client or server side scripting rather than web standards, it
really doesn't belong on the WSG list (see guidelines) - I'd suggest a
general web development source or moving it to the WSG forums for further
Hi,
Are we agreed that the back button *should* take one to the previous page?
I use an internal web application (it's a helpdesk issue tracking
system...not developed by me) where they developers have hijacked/messed
with that back button functionality so I cannot use the back button to get
