tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-867) Palette component should render as an ordinary <select> and update the DOM to provide the normal L&F
Date Tue, 29 Dec 2015 10:19:49 GMT

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

Jochen Kemnade closed TAP5-867.
-------------------------------
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> 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)

Mime
View raw message