Closed Bug 1108893 Opened 9 years ago Closed 9 years ago

[User story] As a desktop client user in a room, I can send/receive text messages with the other room participant.

Categories

(Hello (Loop) :: Client, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
backlog backlog+

People

(Reporter: RT, Unassigned)

References

()

Details

(Whiteboard: [chat])

User Story

As a desktop client user in a room, I can send/receive text messages with the other room participant.

* No persistence of text messages after when the last person leaves the conversation (if A messages B, B leaves and then rejoins, the message is still there so long as A has stayed in the conversation)
* Messages can only be exchanged when in a room.
* In-room text message history available for the duration of the room only

Acceptance criteria:
* When in a room alone:

**[P1]The chat edit box is disabled until someone else joins 

**[P1]If the room has contextual information, the contextual info appears in a speech bubble originating from the right for the link generator (a speech bubble originating from the left for the link clicker).


* When in a room with someone else:

**[P1]If the user has not used chat yet in this session, an indication "Type here..." appears in the chat edit box. This disappears once the user selects the chat area and won't appear again for the rest of the session once the user validates his first message sent

**[P1] If the room has contextual information, the contextual info appears in a speech bubble originating from the right for the link generator (a speech bubble originating from the left for the link clicker). A gear icon in the existing toolbar (right aligned) allows accessing to the context edition view. 

**[P1] When a message is submitted or received for the first time, slide up chat history display with a smooth animation to extend the height of the conversation window

**[P1] New messages appear in speech bubbles with smooth transitions, older messages scroll up. The speech bubble originates from the right for the user's messages and from the left for messages from the link clicker. A sound accompanies new messages received

**[P2] Every minute a timestamp is inserted next to a speech bubble. The timestamp only appears once per minute and any subsequent messages during that minute do not have a timestamp
      No description provided.
Blocks: 1108892
User Story: (updated)
backlog: --- → Fx40+
need UX and the SDK to be actionable.  but a high feature desired towards Fx40
backlog: Fx40+ → backlog+
Rank: 40
Priority: -- → P4
Whiteboard: [Fx40 want]
Flags: firefox-backlog+
Whiteboard: [Fx40 want] → [text][Fx40 want]
Rank: 40 → 23
Priority: P4 → P2
RT's going to attach the URL's to Sevaan's UX to this bug
Flags: needinfo?(rtestard)
User Story: (updated)
User Story: (updated)
User Story: (updated)
Hi Mark, WRT the ability to edit context once chat gets implemented the UX assumes that the visual refresh is done (Gear icon over the video in conversation window).

Given that we won't have visual refresh done in Fx40 we need to find a temporary solution and it would be great to have your views regarding different options we discussed with Sevaan:
1 Implement the drop-down chat menu and make it an option part of that menu for link generators only
2 Temporary gear icon in the corner of the chat box, and leave emoji out for now.

1 is ideal since it won't be throw-away work but I'm not sure if it's realistic to have this done in Fx40.
Thanks for your thoughts!
Flags: needinfo?(standard8)
(In reply to Romain Testard [:RT] from comment #5)
> 1 Implement the drop-down chat menu and make it an option part of that menu
> for link generators only
> 2 Temporary gear icon in the corner of the chat box, and leave emoji out for
> now.
> 
> 1 is ideal since it won't be throw-away work but I'm not sure if it's
> realistic to have this done in Fx40.

I'm not sure a gear icon would be that difficult to add. Especially to the existing toolbar. However if we definitely don't want to do that, then option 1 would be reasonable in the interim.
Flags: needinfo?(standard8)
> I'm not sure a gear icon would be that difficult to add. Especially to the
> existing toolbar. However if we definitely don't want to do that, then
> option 1 would be reasonable in the interim.

Thanks Mark.
A gear icon in the existing toolbar sounds OK, Sevaan is that fine with you for Fx40?
Flags: needinfo?(sfranks)
A gear icon in the existing toolbar is fine. But right-aligned, not next to the camera and mic.
Flags: needinfo?(sfranks)
Thanks, added those details in the US field:

**[P1] If the room has contextual information, the contextual info appears in a speech bubble originating from the right for the link generator (a speech bubble originating from the left for the link clicker). A gear icon in the existing toolbar (right aligned) allows accessing to the context edition view.
User Story: (updated)
Whiteboard: [text][Fx40 want] → [chat]
Sevaan, now that you've advanced more on the Web sharing UX front and given that IM is part of the Web sharing UX, can you confirm that there are no UX changes needed to this IM UX spec before it gets implemented?
Flags: needinfo?(sfranks)
Confirmed.

One caveat, the visuals for the chat work should come from the refresh work in Bug 1138445. The new chat look and feel can just be appended to the bottom of the current window design (like so: http://i.sevaan.com/image/1A2W0s1q1y0g).
Flags: needinfo?(sfranks)
Rank: 23 → 20
Depends on: 1171940
Depends on: 1171962
Depends on: 1172452
Rank: 20 → 12
Priority: P2 → P1
No longer depends on: 1172452
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: WORKSFORME → ---
Flags: firefox-backlog+ → firefox-backlog-
User Story: (updated)
Resolving since all dependent bugs apart from bug 1171962 (chat metrics) are resolved.
Bug 1171962 will be addressed in a different release.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.