987454 - [Messages] The sent message is not painted after sending

Status: RESOLVED WORKSFORME

(Core :: Panning and Zooming, defect)

Description

[Dietrich Ayala (:dietrich)]

hrm, i touched the screen and it painted the rest of the way so couldn't get the screenshot.

i hit send, the message sent.

but the visible message bubble was just a white line. then when i touched it, the whole sent message was visible.

Comment 1

[Julien Wajsberg [:julienw]]

Dietrich, which Gecko/Gaia version do you use?

Comment 2

[Dietrich Ayala (:dietrich)]

Oh sorry, bad bug filer!

Using master (1.5) build from 3/24.

Comment 3

[Gabriele Svelto [:gsvelto]]

I think I encountered this too on my Peak. I sent an MMS message, got a reply, then replied again and when my reply was sent the bubble wasn't shown. This was with Geeksphone master build from the 21st of March.

Comment 4

[Julien Wajsberg [:julienw]]

Yeah, I see this too. This looks like a painting or APZC issue.

As soon as the message is 2 lines, I see the issue.

So here is a STR:
* open the Messages app
* open an existing thread
* send a message with 2 lines

Kats, can you have a look?

Comment 5

[Julien Wajsberg [:julienw]]

Attachment: 2014-03-26-18-58-53.png

Comment 6

[Julien Wajsberg [:julienw]]

QAWanted: does that happen on 1.4?

Comment 7

[Kartikaya Gupta (email:[e-mail])]

Is there a way to reproduce these STR without a SIM card? I can make local changes to my codebase if needed.

Comment 8

[Julien Wajsberg [:julienw]]

Jason, I'm waiting for a qawanted for 5 days here, maybe because it's not in the Firefox OS Product? Could you help? Thanks!

Kats, I'll have a look.

Comment 9

[Julien Wajsberg [:julienw]]

Actually, I don't reproduce it anymore on a current 1.5. Dietrich, do you still see this on a newer build?

Now I'd like to know whether it happens on 1.4 though...

Comment 10

[Dietrich Ayala (:dietrich)]

I reproduced this only once ever.

Comment 11

[Jason Smith [:jsmith]]

(In reply to Julien Wajsberg [:julienw] (away until March 24) from comment #8)
> Jason, I'm waiting for a qawanted for 5 days here, maybe because it's not in
> the Firefox OS Product? Could you help? Thanks!
> 
> Kats, I'll have a look.

Note for the future - in order to get onto the qawanted queries, you either need to have:

* A blocking flag set
* In the Firefox OS product

So in this bug's case, I'd flag the blocking flag as backlog if it's worth fixing, as that will cause this bug to show up in our bug queries.

Comment 12

[Julien Wajsberg [:julienw]]

QA: please test the STR in comment 4 in 1.4. Thanks !

Comment 13

[Kartikaya Gupta (email:[e-mail])]

Please let me know if you still see this with bug 1010119 applied.

Comment 14

[Julien Wajsberg [:julienw]]

Jason, looks like this bug is still not showing up in your queries :)

I'll close it now because I clearly don't reproduce it now, but I still want to know how qawanted works for this type of bugs.

Comment 15

[Jason Smith [:jsmith]]

It actually is in our queries, it's just not on the top of our priority queue.