You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2007/12/06 19:56:58 UTC

[jira] Updated: (WICKET-546) SubmitLink issue : Need for handling user's own onclick javascript call + default && modification in onComponentTag call.

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

Frank Bille Jensen updated WICKET-546:
--------------------------------------

    Fix Version/s:     (was: 1.3.0-rc2)
                   1.3.0-rc3

> SubmitLink issue : Need for handling user's own onclick javascript call + default  &&  modification in onComponentTag call.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-546
>                 URL: https://issues.apache.org/jira/browse/WICKET-546
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.4
>         Environment: Any OS 
>            Reporter: swaroop belur
>            Priority: Minor
>             Fix For: 1.3.0-rc3
>
>
> Wicket version 1.2.4
> Note:  The scenario explained below works perfectly well for a Link.
> Usage :
>  I am using a submit Link in my form to perform a delete operation .
> I disable the link when there is nothing to delete
> [ I maintain a list for this ] and when the user checks some items to
> be deleted , i enable the link and add  a  onClick attribute to call a javascript
> confirmation box via a behavior. Finally i use AjaxRequestTarget.addComponent to render.
> Problem :
> Wicket complains that the delete link cannot be found even though i set
> markupid to true in all relevant places.
> So while debugging i figured out that  onComponentTag of SubmitLink
> does not call super.onComponentTag . By introducing this call in the method,
> I could see the id value[markup id] in  source code.
> HOWEVER this did not solve my problem fully because onClick did not
> call my Javascript function. So on examining the Ajax Debug window
> output, I could see 2 onclicks added for submitlink response.
> This issue needs to address the following 2 questions...
> 1> why doesnt current  onComponentTag call super.onComponetTag ?
> 2> How do i ensure that my javascript call gets invoked before the submit operation? 
> -Thanks
> swaroop belur

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.