924163 - [SMS] Recipient labels go blank when you turn off phone screen and turn it back on

Status: RESOLVED DUPLICATE of bug 918671

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

Description

[Evelyn Eastmond [:evhan55]]

Steps:

1. Open SMS App
2. Enter a few recipients in the To: field
3. Turn off the phone screen by pressing power button
4. Turn on the phone screen, back to SMS app

Expected: Recipients list looks as before
Actual: Recipients list has same labels as before, but they are empty.  Tapping anywhere in the app fills the labels in again

Comment 1

[Evelyn Eastmond [:evhan55]]

Also seems to happen when you leave and come back to the SMS app

Comment 2

[Jason Smith [:jsmith]]

Is this reproducible on a 1.2 shipping device? Probably a regression if that's true.

Comment 3

[Rick Waldron [:rwaldron]]

There are strange focus-related things happening that extend beyond this problem (but include as well)

Comment 4

[Julien Wajsberg [:julienw]]

this is bug 918671.

If one of you has time to make a reduced testcase and share it on bug 918671, it would be awesome, as the Graphics Team asked me this but I doubt I'll find time to do it with all my due reviews...

Comment 5

[Evelyn Eastmond [:evhan55]]

What is a reduced test case?  I went to look at 918671 and saw the one you tried to make, but I don't see requests from the Graphics Team in there or know exactly how to make a reduced test case.  I'll be glad to try, though.

Comment 6

[Jason Smith [:jsmith]]

(In reply to Evelyn Eastmond [:evhan55] from comment #5)
> What is a reduced test case?  I went to look at 918671 and saw the one you
> tried to make, but I don't see requests from the Graphics Team in there or
> know exactly how to make a reduced test case.  I'll be glad to try, though.

A reduced test case is a HTML/CSS/JS fileset that can reproduce the target bug with the minimal amount of code required. This allows a platform developer to test the bug out with the noise of unrelated code outside of the picture, which greatly improves efficiency of fixing the target bug.

Comment 7

[Evelyn Eastmond [:evhan55]]

(In reply to Jason Smith [:jsmith] from comment #6)
> (In reply to Evelyn Eastmond [:evhan55] from comment #5)
> > What is a reduced test case?  I went to look at 918671 and saw the one you
> > tried to make, but I don't see requests from the Graphics Team in there or
> > know exactly how to make a reduced test case.  I'll be glad to try, though.
> 
> A reduced test case is a HTML/CSS/JS fileset that can reproduce the target
> bug with the minimal amount of code required. This allows a platform
> developer to test the bug out with the noise of unrelated code outside of
> the picture, which greatly improves efficiency of fixing the target bug.

Oh, thank you!

Comment 8

[Julien Wajsberg [:julienw]]

A good start could be to create a new app, extract the broken view with all the markup and css, with recipients already added, and see if the problem still reproduces. Also you can see if the problem reproduces with that page loaded in the Browser or if it's only in an app.

And then remove as much markup and css as possible while seeing the bug.

Comment 9

[Rick Waldron [:rwaldron]]

(In reply to Julien Wajsberg [:julienw] (in MozSummit until next monday) from comment #8)
> A good start could be to create a new app, extract the broken view with all
> the markup and css, with recipients already added, and see if the problem
> still reproduces. Also you can see if the problem reproduces with that page
> loaded in the Browser or if it's only in an app.

For repro in browser, I've tried:

- new tab, swap back and forth
- alt-tab between two windows
- letting the actual display sleep


None of these will repro the issue on desktop

Comment 10

[Julien Wajsberg [:julienw]]

When I said "browser" I meant the "Browser app" :)