[ 
https://issues.apache.org/jira/browse/WICKET-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kamil updated WICKET-6507:
--------------------------
    Description: [The problem occured to be somewhere else. I've created 
separate issue for clarity]  (was: This bug is weird, but it has probably 
something to do with race condition.
I recorded a screencast, so you can clearly see what is wrong.
When I have some computation directly in "onSubmit" method, then JS alert is 
invoked properly. If I try to move computation somewhere else (here I just do 
"extract method" refactoring, but in real life this operation would be executed 
in some top-level panel or service) then JS is not being invoked (good thing: 
this behavior is consistent across all of my tries)!

I attached quickstart so you can try it by yourself. The lines I'm extracting 
are: AbstractWindow#55

)

> Please add additional constructor to FeedbackCollector
> ------------------------------------------------------
>
>                 Key: WICKET-6507
>                 URL: https://issues.apache.org/jira/browse/WICKET-6507
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 8.0.0-M8
>            Reporter: Kamil
>            Assignee: Andrea Del Bene
>
> [The problem occured to be somewhere else. I've created separate issue for 
> clarity]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to