Closed
Bug 878426
Opened 13 years ago
Closed 13 years ago
[SMS] While sending a new SMS,when we click on send button the number and text entered disappear in the screen
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-b2g:leo+)
People
(Reporter: leo.bugzilla.gaia, Unassigned)
Details
(Whiteboard: [TD-45813], TaipeiWW)
Attachments
(3 files)
"1. Title: While sending a new SMS,when we click on send button the number and text entered disappears in the screen
2. Precondition: SMS app should be working
3. Tester's Action: (1) Open the SMS application
(2) Select New message
(3) Send SMS to new number which is not existing in the list
4. Detailed Symptom (ENG.) :Once the send button is pressed the Text and content entered disappears in the screen
5. Expected: The number and content should be shown while sending a new message.
6. Reproducibility: Y
1) Frequency Rate : 100%
7. Gaia Master/v1-train: Reproduced on v1-train and Master
8. Gaia Revision: 86fc1cf08c50090a46fc56c5ffa0e7c07cfb1386
9. Personal email id: sasikala.paruchuri@gmail.com"
Hi,
Please find the screenshot attached for the issue.
The Number and text entered disappears while sending a New message.
Thanks,
Leo
Severity: minor → blocker
blocking-b2g: --- → leo+
Priority: -- → P1
Target Milestone: --- → 1.1 QE2 (6jun)
Comment 2•13 years ago
|
||
This is also present in 1.0.1, and is intentional. It stops the user from being able to send the message twice. The recipients entry should shortly become the header, and the message that was sent should show up in the thread.
This is happening when we are sending a message to a new number which is not existing in the thread_list.
(In reply to Corey Frang [:gnarf] [:gnarf37] from comment #2)
> This is also present in 1.0.1, and is intentional. It stops the user from
> being able to send the message twice. The recipients entry should shortly
> become the header, and the message that was sent should show up in the
> thread.
Comment 4•13 years ago
|
||
(In reply to Leo from comment #3)
> This is happening when we are sending a message to a new number which is not
> existing in the thread_list.
>
> (In reply to Corey Frang [:gnarf] [:gnarf37] from comment #2)
> > This is also present in 1.0.1, and is intentional. It stops the user from
> > being able to send the message twice. The recipients entry should shortly
> > become the header, and the message that was sent should show up in the
> > thread.
If the screen stuck in empty status for a few second, I'll tend to agree that this is a bug. But as far as I know, the behavior we have would just like Corey's description. Could you give a precise description about how long did you stuck in the status like your screen shoot?
(In reply to Steve Chung from comment #4)
> (In reply to Leo from comment #3)
> > This is happening when we are sending a message to a new number which is not
> > existing in the thread_list.
> >
> > (In reply to Corey Frang [:gnarf] [:gnarf37] from comment #2)
> > > This is also present in 1.0.1, and is intentional. It stops the user from
> > > being able to send the message twice. The recipients entry should shortly
> > > become the header, and the message that was sent should show up in the
> > > thread.
>
> If the screen stuck in empty status for a few second, I'll tend to agree
> that this is a bug. But as far as I know, the behavior we have would just
> like Corey's description. Could you give a precise description about how
> long did you stuck in the status like your screen shoot?
Hi Steve Chung,
1.After entering the number and text,when we click on send button the text and the number entered disappears.If we go back and check the Sent message is shown in the thread_list.
2.If we send the message to the same number,even after receiving the notification for the message,the the screen is shown as empty and we can able to see the messages once if you go back to thread_list.
Thanks,
Comment 6•13 years ago
|
||
Leo - RE: #2, I can't reproduce this. Every message I send, eventually, if I do nothing, ends up on the right screen with the recipient in the header and the message shown. Also, receiving what notification? I don't believe we are creating a notification for sending a message?
Also - copying some chat from IRC regarding this:
11:38 gnarf: dietrich: 878426 is pretty easy to reproduce - just send a message to a new thread, you'll see an empty screen for ~1-2 seconds while we send the message and wait for gecko to give us the 'sending' event
11:38 gnarf: empty screen = empty inputs on the composer screen
11:38 gnarf: we clear them out to prevent any possible double-tap-double-send
11:39 gnarf: but then the new thread hasn't been created yet - so there isn't anything to show until gecko catches up and sends us the event telling us we sent/failed/are trying to send
11:40 gnarf: THEN we show them the screen with the recipient's name in the header, and a comment box, and the sent message
11:40 gnarf: just wanted to let you know that this is a tricky one
11:40 dietrich: do we need ux to think about a workaround UI during that period?
11:41 gnarf: I'm not sure what we can do about this, we did some trickery before that we might be able to bring back, but we don't have a thread ID - so it's harder now that everything is based in threads not recipients - thats why what we did before isn't there anymore
11:42 dietrich: i'd be fine with some app-modal "wait, something is happening" thing for now
11:43 gnarf: I'll post some more info on the bug, and suggest that as an alternative, and cc ayman?
I'm going to do some investigating to the return value of the send commands - I'm wondering if gecko might be passing back some information we could use earlier in the game to at least push them to the proper "thread"
Assignee: nobody → gnarf37
Flags: needinfo?(aymanmaat)
Corey Frang - Receiving a Notification meaning try to send a message to the same number(itself),once the message is received,we will get a notification for the sent message that is the one which i have mentioned in the second scenario in #comment 5
Comment 8•13 years ago
|
||
(In reply to Leo from comment #7)
> Corey Frang - Receiving a Notification meaning try to send a message to the
> same number(itself),once the message is received,we will get a notification
> for the sent message that is the one which i have mentioned in the second
> scenario in #comment 5
I still can't reproduce this... The message shows up properly
Comment 9•13 years ago
|
||
I am am able to reproduce this bug, but only for a split second.
From a UX PoV there are three undesirable events occurring in-between the send button being pressed and the message thread being created:
1) screen reverts to vanilla 'new message' screen
2) word suggestions panel vanishes leaving a gap through which the wall paper is visible.
3) message thread at first renders with 'new message' in the header before populating it with the detail of the contact.
These three perceivable events make the system seem broken and need to be addressed… unfortunately its more than just implementing some 'wait, something is happening' feedback. We already have such feedback in the thread just before error state as you can see.
refer to my attached video.
Flags: needinfo?(aymanmaat)
Comment 10•13 years ago
|
||
(video too big to attach - waiting for it to upload to dropbox so i can share a link)
Comment 11•13 years ago
|
||
link to video in dropbox.
https://www.dropbox.com/s/zpovf70vsj9z6ux/send_flow.MOV
reference comment 9
Updated•13 years ago
|
Assignee: gnarf37 → waldron.rick
Comment 12•13 years ago
|
||
Preventing double tap double send could be done by disabling the button instead, right ?
Updated•13 years ago
|
Target Milestone: 1.1 QE2 (6jun) → 1.1 QE3 (24jun)
| Reporter | ||
Comment 13•13 years ago
|
||
Hi Julien,
I will upload the video for this defect.
The number and text entered disapperas from the screen when the send button is pressed,message is sent but the same screen appears all the time.
Thanks,
| Reporter | ||
Comment 14•13 years ago
|
||
Please check the attached video.
1.After entering the number and text,click on send button
2.The text and the number entered disappers when user clicks on send button.
3.The screen is same everytime even when the message is sent.
Expected:
1.After clicking on the send button,the message sending icon should be shown which is working for second message.
Comment 15•13 years ago
|
||
The video is showing a real bug, but I sadly don't reproduce it...
I wonder if that's not related to Bug 882899 (which was merged to master a few hours ago) though.
Leo, do you have meaningful logcat information ? (meaningful = anything related to the sms app)
blocking-b2g: leo+ → leo?
Flags: needinfo?(leo.bugzilla.gaia)
Comment 16•13 years ago
|
||
(sorry for the leo? renomination, didn't want to do this)
| Reporter | ||
Comment 17•13 years ago
|
||
Hi Julien,
Able to reproduce this even in master code.
Gaia Revision:20c8fb29caf13e5a4530ba5c7b837a849c79c91b.
Flags: needinfo?(leo.bugzilla.gaia)
| Reporter | ||
Comment 19•13 years ago
|
||
Hi Julienw,
Please find the logcat logs attached for this issue.
Thanks,
Flags: needinfo?(leo.bugzilla.gaia)
Comment 20•13 years ago
|
||
The relevant line is
06-18 17:46:42.580: E/GeckoConsole(1631): [JavaScript Error: "TypeError: Threads.active is undefined" {file: "app://sms.gaiamobile.org/js/thread_ui.js" line: 1225}]
Thanks, this is very helpful !
Comment 21•13 years ago
|
||
Hi Julien, will you be working on this or is Rick still on this one?
Correcting flag per comment 16
blocking-b2g: leo? → leo+
Whiteboard: [TD-45813] → [TD-45813], TaipeiWW
Updated•13 years ago
|
Assignee: waldron.rick → nobody
| Reporter | ||
Comment 22•13 years ago
|
||
This issue is not reproducible in the Latest binary.
Thanks,
Comment 23•13 years ago
|
||
So, this may have been fixed in another bug ?
I kind of remember this error message, but I don't remember which bug it was. Closing it then :)
(love closing leo+ like this ;) )
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•