Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.2.0.GA
-
Fix Version/s: 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:IF 3.x
Description
The null value handling in ace:dataTable filtering is such that nulls are always treated as lower than the value they are being compared against- even another null, causing erroneous behaviour, of course.
Also this handling is so early that a custom Comparator can't override this behaviour. This null value handling shouldn't have any effect when a custom comparator is declared.
Also this handling is so early that a custom Comparator can't override this behaviour. This null value handling shouldn't have any effect when a custom comparator is declared.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Revision #33610
Committed by nils.lundquist
Moments ago
ICE-9024- ace:dataTable filtering comparator leaves null input unhandled when custom comparator declared. Null inputs now correctly represented as equivalent.