Call: does not save the current state

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Call: does not save the current state

Damien Cassou-3
Hi,

imagine your component renders a form and an anchor calling another
component. When the other component answers, the fields previously
filled by the user in the form are emtpy again.

Is this a bug ? Is this something Seaside might implement ?


Thank you
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Call: does not save the current state

tblanchard
Seaside generates unique urls - so coming back from the called  
component looks like a different page to the browser and the form  
values cache in the browser won't recognize that form as being "the  
same".  Because you are navigating using an anchor, the values are  
never submitted to seaside by the browser and so you can't cache them  
either.

The likely fix is to remove the href from the anchor and have it do a  
form.submit onclick to submit the form values so you can cache them  
in your session.

On Jul 16, 2006, at 4:51 AM, Damien Cassou wrote:

> Hi,
>
> imagine your component renders a form and an anchor calling another  
> component. When the other component answers, the fields previously  
> filled by the user in the form are emtpy again.
>
> Is this a bug ? Is this something Seaside might implement ?
>
>
> Thank you
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Call: does not save the current state

Damien Cassou-3
Thank you for this clear and interesting answer.

Bye

Todd Blanchard wrote:

> Seaside generates unique urls - so coming back from the called component
> looks like a different page to the browser and the form values cache in
> the browser won't recognize that form as being "the same".  Because you
> are navigating using an anchor, the values are never submitted to
> seaside by the browser and so you can't cache them either.
>
> The likely fix is to remove the href from the anchor and have it do a
> form.submit onclick to submit the form values so you can cache them in
> your session.
>
> On Jul 16, 2006, at 4:51 AM, Damien Cassou wrote:
>
>> Hi,
>>
>> imagine your component renders a form and an anchor calling another
>> component. When the other component answers, the fields previously
>> filled by the user in the form are emtpy again.
>>
>> Is this a bug ? Is this something Seaside might implement ?
>>
>>
>> Thank you
>> _______________________________________________
>> Seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside