[
https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.s...
]
Matej Novotny commented on RF-13133:
------------------------------------
Verified, issue can be closed.
ExtendedDataTable: filterType=custom doesn't work when mixing
custom and built-in filter columns
------------------------------------------------------------------------------------------------
Key: RF-13133
URL:
https://issues.jboss.org/browse/RF-13133
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tables
Affects Versions: 4.3.1
Environment: Tomcat 7, Mojarra 2.1.21
Reporter: dako ak
Assignee: Brian Leathem
Labels: testcase_provided
Fix For: 4.3.4, 5-Tracking
Original Estimate: 1 hour
Remaining Estimate: 1 hour
According to my appended test project:
I have a simple extendedDataTable with one column (firstName) with a filter input
component within the header. This is the default filter input created by the
extendedDataTable. The second column (city) has a filterType="custom" and an
inputText componenent within the header. The filterType attribute with value
"custom" is ignored because the default input text is rendered too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira