cancel callback bug?

> Anybody think that's a bug?
>
> http://joachimtuchel.wordpress.com/2010/03/05/seaside-3-0-and-cancel-buttons/
>
> I guess the assumption is that your value callbacks don't have
> non-backtrackable effects or something but that seems a bit
> limiting...
>
> Julian
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>

> That's not what WACallbackFunctionalTest is showing. After evaluating
> the callback block a render notification is thrown and no other
> callback is evaluated.
>
> The point that you have to define an empty callback to make the
> callback working is correct though, maybe that's what confused the
> writer? Probably we should add an empty block by default for cancel
> callbacks?
>
> Lukas
>
>
>
>
>
>
>
>
> On 5 March 2010 17:24, Julian Fitzell <[hidden email]> wrote:
>> Anybody think that's a bug?
>>
>> http://joachimtuchel.wordpress.com/2010/03/05/seaside-3-0-and-cancel-buttons/
>>
>> I guess the assumption is that your value callbacks don't have
>> non-backtrackable effects or something but that seems a bit
>> limiting...
>>
>> Julian
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>