> > Now consider applications (as opposed to pages) with very rich state of > undo/redo like a content creation app (i.e. editor). >
Then the content creation/edit tool should have undo/redo controls. Because thats where they belong to. > It is entirely possible for the user to hit the back button (looking for > undo) > Then this user has used the internet the first time ever. No one will treat these browser controls as undo/redo. These controls are always in the navigation area of a browser: back, forward, reload, enter url. > and the result will be that he loses all his work so far. > If the user accidentally hits browser back button and you don't want to loose the work then you should implement autosave. There is literally no good reason to redefine the meaning of browser controls. But this is getting off-topic :) -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
