Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-6823

Contact Reference field in New Relationship broken in IE when using mouse

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Major
    • Resolution: Fixed/Completed
    • Affects Version/s: 3.2.3
    • Fix Version/s: 3.3.alpha
    • Component/s: Core CiviCRM
    • Labels:
      None

      Description

      When using the mouse to select a looked-up contact in the New Relationship, the field does not properly set the contact and therefore does not change the button to be "Quick Save" from "Search" or becomes "Search Again". Consequently, you cannot save the relationship - instead, it tries to search for the contact (and usually doesn't find one since the text doesn't match a name). If you use arrow keys and select the contact by hitting the Enter key, everything works.

      Here are steps:
      1. Open any contact record
      2. Go to Relationships and click New Relationship
      3. Pick a relationship type of "Spouse of"
      4. Start typing in the "Find Target Contact" field - when the list comes up, select the contact by clicking on it using the left mouse button
      5. Notice quick change of the buttons, but the button right below becomes "Search Again" or stays as "Search" instead of switching to "Quick Save"
      6. Try saving the relationship - instead of saving, it does a search for a contact and does not find a result

      Run through the same steps, but in step 4, do not select using the mouse - instead select by using arrow keys and hitting Enter or Tab. Now everything will work as expected.

      See attached screenshots if they help.

        Attachments

          Activity

            People

            • Assignee:
              rajan Rajan P Mayekar
              Reporter:
              pbarmak Paul B
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: