tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin J. Menard, Jr. (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Commented: (TAPESTRY-630) PropertySelection "listener" parameter does nothing
Date Sat, 10 Sep 2005 03:28:30 GMT
    [ http://issues.apache.org/jira/browse/TAPESTRY-630?page=comments#action_12323101 ] 

Kevin J. Menard, Jr. commented on TAPESTRY-630:

Then it should not complain if you specify a listener parameter but don't provide a listener
as a value.  It should treat it as it would any other informal parameter.  Should I open another
bug for this?

> PropertySelection "listener" parameter does nothing
> ---------------------------------------------------
>          Key: TAPESTRY-630
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-630
>      Project: Tapestry
>         Type: Bug
>     Versions: 4.0
>     Reporter: Kevin J. Menard, Jr.
>     Assignee: Howard M. Lewis Ship

> The formal "listener" parameter for the PropertySelection listener seems to not do much.
 Specifying the parameter but not having the actual listener method will generate an error
as expected.  However, if a listener is supplied, it is simply never called.  I tested this
by setting onchange="javascript:this.form.events.refresh();" and onchange="javascript:this.form.submit();"
(I did not try this.form.events.submit() since there is a bug with that not actually submitting
> Anyway, it would be nice if the listener would get called.  Changes to PropertySelection
components are often used to update form contents.  Another nicety would be if specifying
a listener automatically provided an onchange value.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message