Tapestry
  1. Tapestry
  2. TAPESTRY-1687

Autocompleter handles null values in a wrong way

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.2, 4.1.3
    • Fix Version/s: 4.1.3
    • Component/s: None
    • Labels:
      None

      Description

      When autocompleter has to handle values that are null or empty then the javascript 'required' validator doesn't work because the datasqueezer squeezes the value with X or S depending if the value is null or empty.

      1. Autocompleter.diff
        2 kB
        Andrea Chiumenti

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568253 ] jira [ 12591325 ]
        Mark Thomas made changes -
        Workflow jira [ 12409748 ] Default workflow, editable Closed status [ 12568253 ]
        Jesse Kuhnert made changes -
        Resolution Fixed [ 1 ]
        Assignee Jesse Kuhnert [ jkuhnert ]
        Status Open [ 1 ] Resolved [ 5 ]
        Andrea Chiumenti made changes -
        Field Original Value New Value
        Attachment Autocompleter.diff [ 12362950 ]
        Andrea Chiumenti created issue -

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Andrea Chiumenti
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development