933367 - [Messages] We should go back to the thread view when we press "back" after a forward

Status: RESOLVED WONTFIX

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

Description

[Julien Wajsberg [:julienw]]

STR:
* longpress an existing message
* select forward
* press the back button
* select "ok" to discard the message

Expected:
* we go back to the previous thread view

Actual:
* we go back to the thread list

Flagging Ayman for advice before doing anything

Comment 1

[ayman maat :maat]

agreed.

Want me update wireframes?

Comment 2

[Julien Wajsberg [:julienw]]

yep, if necessary, but no rush :)

Comment 3

[Steve Chung [:steveck]]

Hi Jenny, any suggestion about this requirement? I think we didn't define this behavior before.

Comment 4

[Vishnu Teja [:ythej]]

Hi Julien,
Looks like an interesting bug.I think many other platforms also have same procedure.I am taking this bug.
Thank you :)

Comment 5

[Julien Wajsberg [:julienw]]

Vishnu, please wait for Jenny's feedback before doing anything.

I wonder if a "forward" should look like an activity (with a cross)?

Comment 6

[Julien Wajsberg [:julienw]]

And maybe we should remove the context menu in a thread when we're in an activity too.

Comment 7

[Vishnu Teja [:ythej]]

Hi Julien,
sure,I will wait for jenny's feedback.
what are the benefits by making it a activity?

Comment 8

[Julien Wajsberg [:julienw]]

The idea is not to make it an activity, but to make it look like it is. But it's only an idea, I don't know if it's good, let's wait for Jenny.

Comment 9

[Jenny Lee]

Hi Julien,

If forward looks like an activity (with a cross), then the expected behavior should be go back to the previous thread view. Right now we're using back arrow on top left, so it feels right to go back to thread list after selecting either "save as draft" or "discard", as it's how it usually works. So I'm inclined to keep the current behavior, let me know if you think otherwise. Thanks!

Comment 10

[Julien Wajsberg [:julienw]]

Let me precise the various STR:

STR1:
1. longpress an existing message
2. select forward
3. press the back button
4. select "ok" to discard the message

=> Here, I think it's weird to go back to the thread list, because we just left the previous thread.

STR2:
1. longpress an existing message
2. select forward
3. send the message
=> we're redirected to the thread for this recipient (or the thread list if we sent the SMS to several recipients, but let's keep this case out of the STR)
4. press the back button

=> Here, I think it feels right to go to the thread list, because when we sent the message the location changed.


I don't really have a strong opinion on this, if you think the current behavior is fine then I'm fine too. But I'd like a second look :)

Comment 11

[Jenny Lee]

Hi Julien,

For STR1 - I think the problem is as described in comment 9, using "back arrow" implies going up a level/layer, so here, moving from thread to thread list feels right. I would prefer if we can keep the "back" behavior consistent =) I'm open to making the change though if we use "cross" so it will be obvious that the screen is temporary, and returning to previous thread makes sense. 
For STR2 - agree with you here!

Thanks!

Comment 12

[Vishnu Teja [:ythej]]

Hi Jenny,
For STR1 - I think, it will be nice if it is something similar to group-view.In group-view we have back action and we go back to thread view when we press the back button.I don't think it will be nice if it is an activity(with a close) because forwarding indirectly means we are creating a new message and that should look like we are in composer panel.By that user may also easily understands that he gonna create a new thread.But with an activity(with a close) may not be that clear to the user.
(I might be completely wrong) :)
Thank you. :)

Comment 13

[Julien Wajsberg [:julienw]]

Hey Teja,

I think Jenny was quite clear about this already :) so let's just WONFIX this bug now!
Thanks for your involvement !