[ https://issues.apache.org/jira/browse/TAP5-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade updated TAP5-867: -------------------------------- Labels: bulk-close-candidate (was: ) This issue has been last updated more than a year ago, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry (5.4-beta-35, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Palette component should render as an ordinary <select> and update the DOM to > provide the normal L&F > ---------------------------------------------------------------------------------------------------- > > Key: TAP5-867 > URL: https://issues.apache.org/jira/browse/TAP5-867 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core > Affects Versions: 5.2 > Reporter: Howard M. Lewis Ship > Assignee: Howard M. Lewis Ship > Labels: bulk-close-candidate > > It should output the elements in default sort order, identifying which are > selected. On the client side, the Tapestry.Palette class can work from there > to reveal hidden buttons and created the "available" column select. > Basically, the structure should be inside largely invisible DIVs (i.e., > matching the current structure), and when the DOM is loaded, the non-selected > options can be moved to a (newly created) <select> (the available list). > The goal is to simplify the generated markup, and allow the Palette to be > used when JavaScript is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)