Uploaded image for project: 'Snowstorm'
  1. Snowstorm
  2. STORM-1975

IM windows occasionally report false typing status.

    Details

    • Type: Defect
    • Status: Closed
    • Priority: Minor
    • Resolution: Released
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
    • Approvals:
      Code Review
    • Test Plan:
      Hide

      For all of the following, you need 2 systems A and B each with an SL account logged in and with a p2p im session established between them (a chat pane showing for that individual - not Nearby or group chat).

      All the times here are approximate ... variations of 1 to 2 seconds in the expected reaction times should not be considered significant.

      Normal Cases

      1. User A begins typing
        • User B should see "A is typing..." in the conversations title bar
      2. User A stops typing
        • After 5 seconds, User B should see the "A is typing..." indicator cleared from the title bar
      3. User A resumes typing
        • User B should see "A is typing..." in the conversations title bar
      4. User A sends a message (return key)
        • User B should see the message, and the "A is typing..." indicator should be cleared from the title bar

      Simulated Failure Cases

      1. Disconnect network from system A
      2. User A begins typing (maintain ~1 character per second)
        • User B should not see "A is typing..." in the conversations title bar
      3. While still typing, reconnect network to system A
        • Within 4 seconds, User B should see "A is typing..." in the conversations title bar
      4. User A stops typing
        • After 5 seconds, User B should see the "A is typing..." indicator cleared from the title bar
      5. User A resumes typing (maintain ~1 character per second)
        • User B should see "A is typing..." in the conversations title bar
      6. While still typing, disconnect network from system A
      7. User A stops typing
        • After 9 seconds, User B should see the "A is typing..." indicator cleared from the title bar
      8. User A resumes typing
        • User B should not see "A is typing..." in the conversations title bar
      9. While still typing, reconnect network to system A
        • Within 4 seconds, User B should see "A is typing..." in the conversations title bar
      10. User A sends a message (return key)
        • User B should see the message, and the "A is typing..." indicator should be cleared from the title bar
      Show
      For all of the following, you need 2 systems A and B each with an SL account logged in and with a p2p im session established between them (a chat pane showing for that individual - not Nearby or group chat). All the times here are approximate ... variations of 1 to 2 seconds in the expected reaction times should not be considered significant. Normal Cases User A begins typing User B should see "A is typing..." in the conversations title bar User A stops typing After 5 seconds, User B should see the "A is typing..." indicator cleared from the title bar User A resumes typing User B should see "A is typing..." in the conversations title bar User A sends a message (return key) User B should see the message, and the "A is typing..." indicator should be cleared from the title bar Simulated Failure Cases Disconnect network from system A User A begins typing (maintain ~1 character per second) User B should not see "A is typing..." in the conversations title bar While still typing, reconnect network to system A Within 4 seconds, User B should see "A is typing..." in the conversations title bar User A stops typing After 5 seconds, User B should see the "A is typing..." indicator cleared from the title bar User A resumes typing (maintain ~1 character per second) User B should see "A is typing..." in the conversations title bar While still typing, disconnect network from system A User A stops typing After 9 seconds, User B should see the "A is typing..." indicator cleared from the title bar User A resumes typing User B should not see "A is typing..." in the conversations title bar While still typing, reconnect network to system A Within 4 seconds, User B should see "A is typing..." in the conversations title bar User A sends a message (return key) User B should see the message, and the "A is typing..." indicator should be cleared from the title bar
    • Release Vehicles/Components:
      Viewer - Communications

      Description

      Sometimes I dont know if someone is really typing or not.


      When one or more of the conversations in a chat floater is a p2p im session, and the other participant is typing, the title bar of the floater displays "[NAME] is typing..." (where [NAME] is the participant who is typing). If they stop typing for long enough or send a message, that title text is removed.

      It is possible for the start and stop typing messages that trigger this behavior to be dropped, leaving this indicator in an incorrect state (the user is no longer typing, but it says that they still are; or the user is typing and it does not say so). This change introduces some additional behavior to recover the correct state after a short time.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              khyota.wulluf Khyota Wulluf
              Extended Group Visibility:
              jira-users
            • Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: