1019526 - [Flame][v1.4][MMS] The editing page display only a picture rather than two times on the same When the same images add to the MMS.

Status: RESOLVED WONTFIX

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

Description

[greatwall2686]

Attachment: IMG_20140603_182237.jpg

* Description: Not display cover when add the same attachments for many times. (This is a suggested bug.)(IMG_20140603_182237.jpg)

* Reproduction steps:
1. Open the message app
2. New a message
3. Tap add attachment icon
4. The same attachments add many times from device

* Expected result:
  Display only once when add the same attachments for many times.

* Actual result:
  Not display cover when add the same attachments for many times.

* Reproduction build:(Buri - Firefox OS V1.4 outside)
 - Gaia      17b102ee8d9a724b62285547cc5f1c5d30bfb01c
 - Gecko     https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/95be84248033
 - BuildID   20140520000201
 - Version   30.0

* Reproduction Frequency
  - 10/10

Comment 1

[Julien Wajsberg [:julienw]]

Sorry, I don't understand the suggestion here...

Comment 2

[Hubert Lu[:hlu] <[e-mail]>]

Hi reporter,
    May I ask what expected behavior you hope for this case? warning message to notify user or others?
    Please also explain "Not display cover....". I really can't understand what it means.

Comment 3

[greatwall2686]

Hi：
 This is  bug mean :Add the same attachment, it is recommended that the display again

Comment 4

[greatwall2686]

Hi Hubert:
  The editing page display only a picture rather than two times on the same When the same images add to the MMS.

Comment 5

[Julien Wajsberg [:julienw]]

Do you mean we should add the attachment only once if the user attaches the same attachment twice ?

NI reporter to confirm.

If the request is this, then it would clearly be a WONTFIX from my side.

Comment 6

[greatwall2686]

My phone's function look like this

Comment 7

[Julien Wajsberg [:julienw]]

If the user does an action to attach the same image twice, then I'll assume he really wants to do it, and I won't prevent it.

Thanks for the bug but we won't fix it :)