[richfaces-issues] [JBoss JIRA] Resolved: (RF-11316) Improve the data model handling in select components
Brian Leathem (JIRA)
jira-events at lists.jboss.org
Wed Aug 17 02:46:20 EDT 2011
[ https://issues.jboss.org/browse/RF-11316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Leathem resolved RF-11316.
--------------------------------
Labels: needs-qe (was: )
Resolution: Done
This is a rather significant javascript change, that effects all select components (select, inplaceSelect, pickList, orderingList), so I'm labeling needs-qe to verify the behavior is as expected.
> Improve the data model handling in select components
> ----------------------------------------------------
>
> Key: RF-11316
> URL: https://issues.jboss.org/browse/RF-11316
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.1.0.Milestone1
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Labels: needs-qe
> Fix For: 4.1.0.Milestone2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The Pick and Ordering list store their clientSelectItem values in a value attribute of the <tr> or <span> element that lists them.
> The Select and InPlaceSelect use the clientSelectItems passed through as a script option, but loop over the list for every loookup.
> Consolidate and improve these approaches by using the clientSelectItems script option, but make use of the jQuery#data() method to store the values in the DOM elements during component initialization.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list