Closed Bug 816583 Opened 12 years ago Closed 12 years ago

The user is not returned to the gallery after sharing a photo by email

Categories

(Firefox OS Graveyard :: Gaia::Gallery, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-basecamp:-, b2g18+)

VERIFIED DUPLICATE of bug 802643
blocking-basecamp -
Tracking Status
b2g18 + ---

People

(Reporter: cbarker, Assigned: alive)

References

Details

(Whiteboard: interaction, ux-p2, v2, testrun 4, testrun 5.1)

The User is not returned to Gallery after successfully sharing a photo by email selected in the gallery. The User is instead being sent to the Homescreen. Repro Steps: 1. Go to the "Gallery" 2. Select a thumbnail from the grid to enter single photo view 3. Select Share from the toolbar at the bottom of the screen 4. Select Email 5. Enter a valid email address to send the selected picture to, then hit send Actual Results: The email is sent successfully, then the user is ejected to the Homescreen Expected Results: The User is sent to their previous position on the thumbnail grid of the Gallery Notes: This also occurs when backing out of the email by using the < button in the top left of the compose email screen Repro'd this 5/5 times
From the Gallery view when sharing a photo the User is returned to email Inbox after sharing a photo via email. User is NOT returned to gallery grid view. Unagi build 20121217070202
Assignee: nobody → alive
blocking-basecamp: --- → ?
Triage: BB-, tracking-b2g18+ nice to have but should not block with this.
blocking-basecamp: ? → -
tracking-b2g18: --- → +
The intended behavior here is that it should return you back to the Gallery app. We should always be returning the user to where the share activity was invoked.
Whiteboard: interaction, ux-p2, BerlinWW
The implication from bug 821852 is that we need to make the disposition of the e-mail share activity 'inline' rather than 'window'. As discussed on bug 802643, this is a seriously non-trivial undertaking for the e-mail app and unlikely to happen for v1. It seems like improving the Gaia system app or what not to just remember the originating app properly is the only viable option at this time, although based on how insistent everyone is about using inline, that may have its own non-trivial-ness.
Removing "BerlinWW" tag in response to scope evaluation from Andrew.
Summary: [B2G][Gallery] The user is not returned to the gallery after sharing a photo by email → The user is not returned to the gallery after sharing a photo by email
Whiteboard: interaction, ux-p2, BerlinWW → interaction, ux-p2, v2
To clarify: Inline activity in window manager is designed to have an iframe got from gecko to cover on an displayed app; Window position activity is similar to open a new app. Improve Gaia system app in activity UI is possible, but it's very unclear now that we should design a new 'position' or do other things like improve activity manifest parameters. Agree to be non-trivial if the core problem is email app couldn't live in inline frames.
Issue repros on Build 20130104070203 Actual: After sharing a picture by pressing send on the email you are taken back to homescreen. Expected: Per test 3626 ...After the photo is shared the user is returned to Grid View.
UCID gallery-028 Test Case located here https://moztrap.mozilla.org/results/case/61015/
Whiteboard: interaction, ux-p2, v2 → interaction, ux-p2, v2, testrun 2
Repros on Unagi device Build ID: 20130115070201 using the december 5th kernel
OS: Other → Gonk (Firefox OS)
Hardware: Other → ARM
Issue repros Build ID: 20130130070201 Kernel: Dec 5 Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/4593f3e765eb Gaia f7f5a0cd17e3d04308cc5850b254947e127122b9
Whiteboard: interaction, ux-p2, v2, testrun 2 → interaction, ux-p2, v2, testrun 4
Resolved duplicate of Bug #802643.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Resolution: WORKSFORME → DUPLICATE
Whiteboard: interaction, ux-p2, v2, testrun 4 → interaction, ux-p2, v2, testrun 4, testrun 5.1
Verified as a dupe of bug 802643
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.