Re: T5: ProgressiveDisplay - Possibly not reloading properly on Safari when user uses browser 'Back' Button

2010-05-27 Thread Chris Darlaston
Thanks Josh, that worked a treat and solved the issue. Josh Canfield wrote: Try adding autocomplete=off on your radio button element. I haven't tried it, but it works for input fields. On Wed, May 26, 2010 at 9:09 AM, Chris Darlaston ch...@2infinity.net wrote: Using cmd-R, I get the

Re: T5: ProgressiveDisplay - Possibly not reloading properly on Safari when user uses browser 'Back' Button

2010-05-26 Thread Chris Darlaston
Using cmd-R, I get the right page shown again. If this is a browser related problem does anyone have any ideas how to get Safari to reload the page or not to cache the radio button information? thanks Chris Howard Lewis Ship wrote: It can be hard to say; too often, the browser

Re: T5: ProgressiveDisplay - Possibly not reloading properly on Safari when user uses browser 'Back' Button

2010-05-26 Thread Josh Canfield
Try adding autocomplete=off on your radio button element. I haven't tried it, but it works for input fields. On Wed, May 26, 2010 at 9:09 AM, Chris Darlaston ch...@2infinity.net wrote: Using cmd-R, I get the right page shown again. If this is a browser related problem does anyone have any

T5: ProgressiveDisplay - Possibly not reloading properly on Safari when user uses browser 'Back' Button

2010-05-25 Thread Chris Darlaston
Hi, I have a t:radiogroup set of buttons in a t:progressivedisplay. On selection of the radio button, another zone is updated (which contains a drop down list) is done via a t:mixins. In Firefox 3, IE 8, it works perfectly and on using 'Back' from the browser, the t:progressivedisplay

Re: T5: ProgressiveDisplay - Possibly not reloading properly on Safari when user uses browser 'Back' Button

2010-05-25 Thread Howard Lewis Ship
It can be hard to say; too often, the browser is doing something clever for you (the way it often fills in user name and password fields for you). Doing a hard refresh (cmd-R) usually clarifies whether the problem is the browser or Tapestry. On Tue, May 25, 2010 at 6:55 AM, Chris Darlaston