Re: [WSG] Re: Where did I come from?

2008-01-20 Thread Joe Ortenzi
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 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?





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Joe Ortenzi
[EMAIL PROTECTED]
www.joiz.com




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***

Re: [WSG] Re: Where did I come from?

2008-01-20 Thread Joe Ortenzi

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 particular standard?


I addition, have you researched that people WANT to go back to the  
site that led them to your web app? sometimes people move on to the  
next site for a reason and really are done with the first one...


Joe

On Jan 19 2008, at 07:18, Simon Cockayne wrote:


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 back where I was before I entered the internal web  
apprather the internal web app page re-renders itself.



The developers of the internal web app are not keen on un-hijacking/ 
un-messing with the back button processing.


A compromise...I thought...would be a button in the page saying,  
for example "Return" (or leave or abandon or exit or something  
TBA)...that would take the user back to the page they were on  
*before* the entered the internal web app.


To accomplish the compromise the web app will need to know/ 
determine what the prior page to the web app was...


Cheers,

Simon

On Jan 18, 2008 2:24 PM, Simon Cockayne < [EMAIL PROTECTED]>  
wrote:

Hi,

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 don't have permission to access it.


NOTE: I don't want to use the History object to go back or  
forward...I just want to know what the previous page was...so I can  
create a button to go back to it...


Cheers,

Simon




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***


Joe Ortenzi
[EMAIL PROTECTED]
www.joiz.com




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***

ADMIN Re: [WSG] Re: Where did I come from?

2008-01-19 Thread James Ellis
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
discussion.


Thanks
James

admin


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***

Re: [WSG] Re: Where did I come from?

2008-01-19 Thread Ron Zisman
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 button behaviour (so it behaves as
expected) on pages that do stuff like loading data by using  
javascript in

hidden iframes?





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Re: Where did I come from?

2008-01-19 Thread Ron Zisman

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 by using  
javascript in

hidden iframes?





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



RE: [WSG] Re: Where did I come from?

2008-01-19 Thread Michael MD
>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? 





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***