On Apr 3, 8:36 pm, Jorge Godoy <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] writes: > > On Tue, 3 Apr 2007 at 17:56, Diez B. Roggisch wrote: > >> On Tuesday 03 April 2007 17:46, George Sakkis wrote: > >>> I have a SingleSelectField with default=-1 that displays correctly the > >>> default item when I visit the respective url. However if I change the > >>> value in the browser and hit reload, the selection stays as is, it > >>> doesn't go back to the default. I tried to make default callable > >>> (default=lambda:-1) but that didn't work either. Any clues ? > > >> I think that's browser behaviour. Or did the HTML source change in between? > > > I'm pretty sure you are right, Diez. My Firefox 2.0 seems to retain > > the value of the form field variables on refresh on all sites, > > not just on my TG application. But I haven't tested this, I've just > > kind of "noticed" it, and been pleased in some cases and annoyed > > in others :) > > I love this behavior. > > When I want to reload the full page to its defaults I use CTRL-R, otherwise I > use F5 to reload it without cleaning my input or going back to default values > in the fields I've already changed.
Maybe you mean CTRL+SHIFT+R ? That did the trick for me after reading http://dailyshortcut.com/2006/12/05/refreshing-with-f5-and-ctrlr-in-firefox-and-ie/. In any case, caching doesn't work for cascading dropdown lists (i.e. using javascript to load the values of one column based on the value of some other column), which is how I noticed the inconsistency. George --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
