[ 
https://issues.apache.org/jira/browse/TAP5-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165947#comment-13165947
 ] 

Hudson commented on TAP5-1773:
------------------------------

Integrated in tapestry-trunk-freestyle #638 (See 
[https://builds.apache.org/job/tapestry-trunk-freestyle/638/])
    TAP5-1773 Add a new OverrideFieldFocus mixin which supersed and deprecate 
the old one FormFieldFocus

mlusetti : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1212270
Files : 
* 
/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/mixins/FormFieldFocus.java
* 
/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/mixins/OverrideFieldFocus.java
* 
/tapestry/tapestry5/trunk/tapestry-core/src/test/app1/OverrideFieldFocusDemo.tml
* 
/tapestry/tapestry5/trunk/tapestry-core/src/test/groovy/org/apache/tapestry5/integration/app1/FormFieldFocusTest.groovy
* 
/tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/Index.java
* 
/tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/OverrideFieldFocusDemo.java

                
> FormFieldFocus mixin passes control name, not client id, to 
> JavaScriptSupport.autofocus()
> -----------------------------------------------------------------------------------------
>
>                 Key: TAP5-1773
>                 URL: https://issues.apache.org/jira/browse/TAP5-1773
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Massimo Lusetti
>              Labels: fields, forms
>             Fix For: 5.3.1, 5.4
>
>
> Noticed this while writing up some documentation about dealing with form 
> focus. This works in simple cases where the control name and the client id 
> often are the same value, but won't work in other cases (especially Ajax 
> ones).
> In addition, it is not clear why this mixin is attached to a Form and takes a 
> Field as a parameter rather than attaching to a Field and taking no 
> parameters?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to