Closed
Bug 1115342
Opened 10 years ago
Closed 9 years ago
[user story] As a desktop client user in a conversation, I want to see contextual information so that I am better prepared and more engaged when entering the conversation.
Categories
(Hello (Loop) :: Client, enhancement, P2)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla40
| backlog | backlog+ |
People
(Reporter: RT, Unassigned)
References
Details
(Whiteboard: [context])
User Story
As a desktop client user in a conversation, I want to see contextual information so that I am better prepared and more engaged when entering the conversation. Acceptance criteria: * When in a conversation (alone or not), the following details about the attached URL get displayed to the desktop client user: - Thumbnail and Favicon of the webpage the URL points to - Content of the <title> tag of the webpage the URL points to - URL * The contextual information in the conversation panel can be closed through the close button (next time the conversation is opened these details will re-appear) * The contextual information in the conversation panel can be edited through the edit button: - Clicking the edit button opens a new panel (slides up from the bottom of the conversation window) - The user can edit the URL and the description of the context - Selecting the tickbox allows changing the context to the context of the currently active tab (gets the URL and title page as a description of the conversation) * Clicking the URL opens the URL in a new tab * Accessing the URL from the conversation window will trigger a Telemetry event
Attachments
(3 files)
2.png
No description provided.
|
Reporter | |
Updated•10 years ago
|
backlog: --- → Fx38?
|
||
Updated•9 years ago
|
User Story: (updated)
Summary: [user story] As a desktop client user in a conversation, I want to access a URL context supporting the conversation so it's more convenient. → [user story] As a desktop client user joining a conversation, I want to see contextual information so that I am better prepared and more engaged and when entering the conversation.
|
|
Reporter | |
Comment 1•9 years ago
|
||
Attaching Sevaan's design
|
|
Reporter | |
Updated•9 years ago
|
User Story: (updated)
|
||
Comment 2•9 years ago
|
||
putting at P5 as it's actively being worked in PM and the creative team to prioritize co-browsing scenarios. it's not actionable to put as higher priority until the scenarios and prioritization and UX are finalized.
Severity: normal → enhancement
Priority: -- → P5
|
|
Reporter | |
Updated•9 years ago
|
backlog: Fx38? → Fx39?
|
|
||
Comment 3•9 years ago
|
||
moving up once the P1's and P2's are done - this is the next priority feature.
Severity: enhancement → normal
backlog: Fx39? → Fx38+
Rank: 30
Priority: P5 → P3
|
|
Reporter | |
Updated•9 years ago
|
User Story: (updated)
|
|
Reporter | |
Updated•9 years ago
|
Summary: [user story] As a desktop client user joining a conversation, I want to see contextual information so that I am better prepared and more engaged and when entering the conversation. → [user story] As a desktop client user alone in a conversation, I want to see contextual information so that I am better prepared and more engaged when entering the conversation.
|
|
Reporter | |
Updated•9 years ago
|
User Story: (updated)
|
|
Reporter | |
Comment 4•9 years ago
|
||
Comment on attachment 8546563 [details]
2.png
Conversation window with context when waiting alone in a room.|
|
Reporter | |
Comment 5•9 years ago
|
||
In-call conversation window with context
|
|
Reporter | |
Updated•9 years ago
|
User Story: (updated)
Summary: [user story] As a desktop client user alone in a conversation, I want to see contextual information so that I am better prepared and more engaged when entering the conversation. → [user story] As a desktop client user in a conversation, I want to see contextual information so that I am better prepared and more engaged when entering the conversation.
|
|
Reporter | |
Comment 6•9 years ago
|
||
Edit context in conversation window
|
|
||
Updated•9 years ago
|
Whiteboard: [context]
|
|
||
Updated•9 years ago
|
backlog: Fx38+ → backlog+
Rank: 30 → 22
Flags: firefox-backlog+
Priority: P3 → P2
|
||
Updated•9 years ago
|
Severity: normal → enhancement
|
|
||
Comment 7•9 years ago
|
||
The only outstanding dependency is telemetry which is blocking the main tracker - bug 1115340 - so I'm calling this fixed. Other issues blocking the release will also block that bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•