Changes between Version 1 and Version 3 of Ticket #5919


Ignore:
Timestamp:
Jun 10, 2008, 2:04:43 AM (11 years ago)
Author:
bill
Comment:

I'm making an executive decision on this one:

As much as possible, getValue() *should* return an invalid string as-is. It shouldn't change behavior due to a field being required/not-required, invalid/valid. The only exception is when the widget maps the displayed value into another value, and there is no mapping (ex: "foo" for a NumberTextBox or "Japan" for a FilteringSelect of U.S. states), in which case getValue() should return the same thing it returns when the field is blank.

Also, getValue() should always return data of the same type. Either always strings, always numbers, or always Dates, where an empty date is represented as null (see #6827, #6922).

As for MappedTextBox, the reason it returns the string as-is is because the subclass needs to override certain methods. MappedTextBox by itself doesn't do any mapping.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5919

    • Property Status changed from new to closed
    • Property Resolution changed from to wontfix
    • Property Summary changed from ValidationTextBox subclasses return different getValues on error to ValidationTextBox: subclasses return different getValues on invalid