Hi Alidra, See here: https://stackoverflow.com/questions/42653378/message-order-cascading-on-html... <https://stackoverflow.com/questions/42653378/message-order-cascading-on-html...> Also, posting your questions on Seaside to the seaside mailinglist is a better idea ;)d cheers Johan
On 30 May 2017, at 10:21, Alidra Abdelghani via Pharo-users <pharo-users@lists.pharo.org> wrote:
From: Alidra Abdelghani <alidrandco@yahoo.fr> Subject: [Seaside] Strange behaviours? Date: 30 May 2017 at 10:21:38 GMT+2 To: pharo-users@lists.pharo.org
Hi all, I just noticed that changing the message send order to an anchor modifies itsâ behaviour :
html anchor with: aString;callback: [doSomething]. -> click on the anchor executes the callback block
html anchor callback:[doSomething];with:aString. -> click on the anchor does not executes the callback block.
Is this a normal behaviour?
I also noticed that instantiating a WAComponent in the same method that calls html render: on it makes the call method in this object fail. See (http://smalltalkhub.com/#!/~Alidra/Seaside_Strange_Call_Behavior <http://smalltalkhub.com/#!/~Alidra/Seaside_Strange_Call_Behavior>) for an concrete example. BTW. I find the name call: quite confusing : you call a method, you pass control to an object. But maybe this is because I am new to Seaside.
Thank you Abdelghani