I can see from where you are coming and there is truth in what you say. Now consider applications (as opposed to pages) with very rich state of undo/redo like a content creation app (i.e. editor). It is entirely possible for the user to hit the back button (looking for undo) and the result will be that he loses all his work so far. This isn't cool either...
On Fri, Jun 6, 2014 at 2:20 PM, Jens <[email protected]> wrote: > Unless you manage to implement undo/redo as back/forward which is very >> cool IMO. >> > > Which would mean users of your app now have one feature less: Navigating > through your app via back/forward like on any other website. Thus your app > is now the exception to everything on the web which totally breaks user > assumptions. > > So IMHO it is pretty uncool ;-) > > > -- 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. > -- Vassilis Virvilis -- 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.
