You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/07/19 03:50:57 UTC

[jira] [Created] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
----------------------------------------------------------------------------------------------------------------------------

                 Key: TAP5-1578
                 URL: https://issues.apache.org/jira/browse/TAP5-1578
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.3, 5.2
            Reporter: Howard M. Lewis Ship


The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068075#comment-13068075 ] 

Hudson commented on TAP5-1578:
------------------------------

Integrated in tapestry-trunk-freestyle #422 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/422/])
    TAP5-1578: Rework how and when FormFragment enables/disables the hidden field

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148548
Files : 
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/javascript/CoreJavaScriptStack.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-init.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tree.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-core.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/mixins/TriggerFragment.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tapestry.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/FormFragmentDemo.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-formfragment.js


> When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1578
>                 URL: https://issues.apache.org/jira/browse/TAP5-1578
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: forms, javascript
>             Fix For: 5.3
>
>
> The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1578.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3

> When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1578
>                 URL: https://issues.apache.org/jira/browse/TAP5-1578
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: forms, javascript
>             Fix For: 5.3
>
>
> The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1578:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1578
>                 URL: https://issues.apache.org/jira/browse/TAP5-1578
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: forms, javascript
>
> The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068075#comment-13068075 ] 

Hudson commented on TAP5-1578:
------------------------------

Integrated in tapestry-trunk-freestyle #422 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/422/])
    TAP5-1578: Rework how and when FormFragment enables/disables the hidden field

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148548
Files : 
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/javascript/CoreJavaScriptStack.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-init.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tree.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-core.js
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/mixins/TriggerFragment.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tapestry.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/FormFragmentDemo.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/t5-formfragment.js


> When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1578
>                 URL: https://issues.apache.org/jira/browse/TAP5-1578
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: forms, javascript
>             Fix For: 5.3
>
>
> The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1578.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3

> When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1578
>                 URL: https://issues.apache.org/jira/browse/TAP5-1578
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: forms, javascript
>             Fix For: 5.3
>
>
> The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (TAP5-1578) When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1578:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1578
>                 URL: https://issues.apache.org/jira/browse/TAP5-1578
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: forms, javascript
>
> The visibility change should take effect immediately, and the animation should lag. Instead, it's the other way around, which means that if the user is quick, the data in the now visible fragment will not be submitted with the rest of the form.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira