Thanks Pat!
On Jan 18 2008, at 17:57, Patrick H. Lauke wrote:
Christian Snodgrass wrote:
You shouldn't always assume that they are just trying to replace
the back button.
They could want to get the referrer for something else.
From the thread starter
.I just want to know what the previous
Thanks David, Glad to see I'm not the only one who read the email
carefully before replying. :-)
My understanding of web standards is that one does not replace/
duplicate what is part of the standard furniture without a GOOD
reason. Replicating functionality that already exists goes against
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
You'd be surprised (maybe not!) as to how few people know about tab
and new windows and use them for this purpose.
I really have to push people in our studio to use these.
Joe
On Jan 19 2008, at 12:11, George S. Williams wrote:
On Sat, 2008-01-19 at 04:38, Designer wrote:
I use this kind
Martin Heiden wrote:
Simon,
on Friday, January 18, 2008 at 15:24 wsg@webstandardsgroup.org wrote:
I am on a webpage...how do I know what page the browser was previously
showing.
I think Javascript History object is the ticket...but STRICT mode in Firefox
seems to tell me that I
I am currently out of the office and will return on Wednesday 23rd January.
Please direct all urgent queries to [EMAIL PROTECTED]
IMPORTANT -
Please consider our environment before printing this email.
This email and any attachments are confidential and may be legally privileged
in which case
