[Seaside] Tasks and reusing components
jfitzell at gmail.com
Sun Feb 28 18:12:32 UTC 2010
On Sun, Feb 28, 2010 at 5:13 PM, Julian Fitzell <jfitzell at gmail.com> wrote:
> Hm... indeed. There is a bug here. I can see what it is but I'm not
> sure what the solution is yet... I'll post back.
> On Sun, Feb 28, 2010 at 12:53 PM, radoslav hodnicak <rh at 4096.sk> wrote:
>> I might add that the code seems to work in 2.8 - it shows page expired, so
>> this is a bug/regression in 3.0
>> On Sat, 27 Feb 2010, radoslav hodnicak wrote:
>>> Ok, I have more problems with this setup, this time with isolating steps.
>>> I have attached a new version of my test code which shows what I'm talking
>>> the #go method is
>>> | result |
>>> self isolate: [result := self call: component1].
>>> self call: (component2 result: result).
>>> steps to reproduce
>>> 1) component1 click link N
>>> 2) component2 don't click OK, use back button
>>> 3) all the links on this page should be expired now, but when I click one
>>> I don't get the "page expired" error, I get component2 as if there was no
>>> To make sure this isn't some browser caching issue, component1 writes to
>>> Transcript before it answers, and indeed there's a line for each back button
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
More information about the seaside