W3C home > Mailing lists > Public > public-webapi@w3.org > January 2006

RE: Ajax Back/Forward History problem - saving document state by document.save()

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Tue, 10 Jan 2006 00:18:36 -0000
Message-ID: <AFDBBEB8-F4FD-4EFB-83AA-FFFB5F6686FE@s15.mail.x-port.net>
To: <public-webapi@w3.org>

It may be too late ;)

Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
b: http://internet-apps.blogspot.com/
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/  

> -----Original Message-----
> From: George Stevens [mailto:gstevens@guidelightsolutions.com] 
> Sent: 09 January 2006 22:46
> To: Mark Birbeck; public-webapi@w3.org
> Subject: RE: Ajax Back/Forward History problem - saving 
> document state by document.save()
> 
> If the back button feels like the right metaphor for the user 
> to use then the issue may be with a webapp's appearance 
> rather than its behavior.  I don't have any question about 
> what is happening if I am viewing an online PDF and hit the 
> back button.  My intent was to leave the adobe application.  
> There are clear visual clues that let me know that I am in 
> the 'application' rather than on a 'page'.  My suspicion is 
> that, just as there has been organic growth of web-navigation 
> skills, there will also develop a set of skills for web-apps 
> and the back button will become a non-issue. 
> 
> George B. Stevens
> Guidelight Business Solutions
> http://www.GuidelightSolutions.com/
> Cell: 512-698-5558
> Office: 512-401-6144 
> 
> 
> -----Original Message-----
> From: public-webapi-request@w3.org 
> [mailto:public-webapi-request@w3.org]
> On Behalf Of Mark Birbeck
> Sent: Monday, January 09, 2006 2:15 PM
> To: public-webapi@w3.org
> Subject: RE: Ajax Back/Forward History problem - saving 
> document state by document.save()
> 
> 
> Vladimir,
> 
> > But it doesn't necessary mean that undo should be performed using 
> > browser's "Back" button.
> 
> That's true, but I'm hoping that it can be an event that can 
> be registered for, and than either allowed through, or acted 
> on and cancelled.
> 
> 
> > I prefer "Back" button to be
> > conditionally disabled...
> 
> You could do that by cancelling the proposed 'back' event.
> 
> 
> > ...and to have "Undo" button inside web application window 
> itself (as 
> > a part of HTML document).
> 
> But there are some situations where 'back' feels like the 
> right metaphor to the user, even if it has the effect of 
> 'undo'. I agree with whoever it was that gave the example of 
> Gmail--how many times have you opened an email, and then 
> pressed 'back' to return to the inbox, only to find yourself 
> navigating away.
> 
> Regards,
> 
> Mark
> 
> 
> Mark Birbeck
> CEO
> x-port.net Ltd.
> 
> e: Mark.Birbeck@x-port.net
> t: +44 (0) 20 7689 9232
> b: http://internet-apps.blogspot.com/
> w: http://www.formsPlayer.com/
> 
> Download our XForms processor from
> http://www.formsPlayer.com/
> 
> 
> 
> 
Received on Tuesday, 10 January 2006 00:19:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT