[User story] As a desktop client user in a conversation, I can start sharing the content of my active tabs from within my conversation so that link clickers can see my active tab. Acceptance criteria: * A new "Share" button is available in the conversation UI * Clicking the "Share" button offers the user a "Share my tabs" option * Clicking the "Share my tabs" option closes the dialog and initiates sharing of the active tab * When "Share my tabs" is active, the following applies: - Opening a new tab opens a new tab with custom content (see mock-ups) - The conversation window does not get shared - If the user selects another tab, the newly selected tab becomes shared in the room. * When sharing is active the "Share" button turns green and the Hello icon turns green. An infobar informs the user how sharing window works. The infobar can be dismissed by the user. A visual indicator, visible whether Firefox is in the foreground or the background informs the user that sharing is active. * Sharing can be stopped by: - Clicking the "Share" button again - Leaving the conversation - Closing Firefox * When sharing becomes inactive the "Share" button turns grey and the Hello icon turns grey
User Story: (updated)
Summary: [User story] As a desktop client user in a room, I can start sharing the content of my active tabs from within my room so that link clickers can see my active tab. → [User story] As a desktop client user in a conversation, I can start sharing the content of my active tabs from within my conversation so that link clickers can see my active tab.
work being broken down currently. likely other teams impacted (which is why the P2 will break down and update based on what is feasible).
backlog: Fx38? → Fx38+
Priority: -- → P2
We'll want to note this feature in 38 if it's ready in Beta.
relnote-firefox: --- → ?
the tech bugs to resolve this have been taken, now it's bug and patch work.
Status: NEW → RESOLVED
Iteration: --- → 39.2 - 23 Mar
Last Resolved: 4 years ago
Resolution: --- → FIXED
bad EPM - this bug is a container for other bugs to keep them orderly. just moving off firefox-backlog+ to firefox-backlog-
Status: RESOLVED → REOPENED
Iteration: 39.2 - 23 Mar → ---
Flags: firefox-backlog+ → firefox-backlog-
Resolution: FIXED → ---
Shell, should this have release notes in 38 or in 39? Is there enough of it ready in 38 to warrant a release note?
(In reply to Liz Henry (:lizzard) from comment #6) > Shell, should this have release notes in 38 or in 39? Is there enough of it > ready in 38 to warrant a release note? Liz please see comments following https://bugzilla.mozilla.org/show_bug.cgi?id=1099241#c4 where we discuss release notes for this feature.
pending discussion at the 38 release meeting on how release notes are handling between 38 ad 38.1. the sharing will be turned off until 38.1 on June 2nd.
Rank: 2 → 20
Flags: firefox-backlog- → firefox-backlog+
Priority: P1 → P2
I've moved the remaining deps to bug 1099241, as effectively this bug is fixed, and the remaining issues are minor. Hence closing this bug. The relnote discussion was help on bug 1099241 so clearing those flags as well.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago → 4 years ago
relnote-firefox: ? → ---
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
You need to log in before you can comment on or make changes to this bug.