You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2011/04/12 11:16:05 UTC

[jira] [Updated] (TAP5-835) Palette keeps resetting order of selected values on page reload

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

Jochen Kemnade updated TAP5-835:
--------------------------------

          Environment: affects Tapestry versions 5.0.x.x through 5.2.x regardless of OS/browser  (was: affects 5.0.18 as well as 5.1.0.5 and current 5.2.0-SNAPSHOT regardless of OS/browser)
    Affects Version/s: 5.2.5

> Palette keeps resetting order of selected values on page reload
> ---------------------------------------------------------------
>
>                 Key: TAP5-835
>                 URL: https://issues.apache.org/jira/browse/TAP5-835
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.2.5, 5.1.0.5, 5.1.0.6, 5.1.0.7, 5.0.18
>         Environment: affects Tapestry versions 5.0.x.x through 5.2.x regardless of OS/browser
>            Reporter: Jochen Kemnade
>            Priority: Minor
>         Attachments: palette-sorting-fix.zip
>
>
> I'm experiencing a problem with tapestry's palette component. I'm using it with the reorder parameter set to true. Reordering the
> selected values works fine and the values are sent to the server in the expected order. However, if the page reloads and I submit the
> containing form again without changing the palette's values, the original order is restored and sent to the server resetting the
> previously arranged order.
> AFAICT, this relates to the hidden form field used by the palette and the updateHidden Javascript method. This method is called whenever the
> order of the selected options is changed. It is not called however when the Palette object is instantiated, so the hidden field keeps the
> sorting that comes from the server. 
> I believe, this could be fixed by calling the updateHidden method at the end of the Tapestry.Palette.initialize method. The following patch
> does this:
> Index: palette.js
> ===================================================================
> --- palette.js  (Revision 755168)
> +++ palette.js  (Arbeitskopie)
> @@ -45,6 +45,7 @@
>          }.bind(this));
>          this.bindEvents();
> +        this.updateHidden();
>      },
>      bindEvents : function()

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