WhatsApp hung when sending a message (with message text floating in middle of window)

RESOLVED WONTFIX

Status

Tech Evangelism
Preinstalled B2G Apps
RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: emorley, Unassigned)

Tracking

({foxfood})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
>> Feature Request Summary:
WhatsApp hung when sending a message (with message text floating in middle of window)

>> Description of feature, or problem to be solved
Using the Z3C foxfooding device. My phone is currently running build number: eng.naoki.20151007.074137, build identifier 20151023101519, however this bug occurred (judging from the screenshot timestamp) the day before the email was sent out about the FOTA, so I would have been on the build before that.

STR:
1) Open a WhatsApp conversation
2) Compose a message reply and press send

Expected:
Message sends and app remains responsive

Actual:
The message text was partially rendered in the middle of the app, but not in a message bubble. The message did not send to the recipient, and the app hung and required me to force kill it, meaning I lost the message I'd spent a while writing. Screenshot to follow.
(Reporter)

Comment 1

2 years ago
Created attachment 8684568 [details]
WhatsApp screenshot

Screenshot of the hung window.

The text floating in the middle was at the end of the composed message (ie followed the text you can see that is still in the message input area).
(Reporter)

Updated

2 years ago
See Also: → bug 1180920

Updated

2 years ago
QA Whiteboard: [foxfood-triage]
Component: Gaia::Feedback → Preinstalled B2G Apps
Product: Firefox OS → Tech Evangelism
As Bill Walker notes in bug 1177394, comment 24, he has directed his engineering team to stop work on RunWhatsApp in favor of our new focus on progressive web apps, so we won't have time to spend on this.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.