Closed Bug 804396 Opened 12 years ago Closed 12 years ago

[system] screenshot of apps that never brought to foreground is distorted

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nhirata, Unassigned)

References

Details

(Whiteboard: [label:system/cards_view][label:system/window_management])

Attachments

(2 files, 1 obsolete file)

Attached image screenshot
## Environment :
Otoro phone, build 2012-10-22
Taken from default.xml in b2g-distro: 
* "platform_build" revision= 0d6d050bc37d3167cc82a1885fd7660456bb0f4e
* "gaia" revision= cf533e66c4c589478f5addc53cab2d9a4853402b 
* "releases-mozilla-aurora" revision= 471232068fc202ba54b12eaf5b7de70aef4a079e
* "gonk-misc" revision= da6e50508245d023166e0c04369200e5bb898220

  
## Repro :
1. launch clock app
2. set alarm for 1 min into future
3. long tap home button and swipe clock app closed
4. wait for alarm
5. long tap home button

## Expected :
1. full shot of clock app

## Actual :
1. part of the clock app enlarged

## Note :
1. see screenshot
Update title -- we we need to ensure the size of the iframe is set properly as we create the frame -- not until we launch it.
Summary: [Clock] if an alarm goes off while the clock app has been killed, the task manager will show the clock app distorted. → [system] screenshot of apps that never brought to foreground is distorted
Whiteboard: [label:system/cards_view][label:system/window_management]
https://github.com/mozilla-b2g/gaia/pull/5971

[Approval Request Comment]
Bug caused by (feature/regressing bug #): launching app with system message mozChromeEvent; not bring app to foreground as we launch it
User impact if declined: as described in STR
Testing completed: testing done on Otoro
Risk to taking this patch (and alternatives if risky): there shouldn't be any risk.
Attachment #674520 - Flags: review?(dflanagan)
Attachment #674520 - Flags: approval-gaia-master?(21)
Comment on attachment 674520 [details]
Pointer https://github.com/mozilla-b2g/gaia/pull/5971

r- See the comment on github
Attachment #674520 - Flags: review?(dflanagan) → review-
Thanks for the comment, I didn't trace the calls closely enough. Some comment is addressed on the same pull request.
Attachment #674520 - Attachment is obsolete: true
Attachment #674520 - Flags: approval-gaia-master?(21)
Attachment #674948 - Flags: review?(dflanagan)
Attachment #674948 - Flags: approval-gaia-master?(21)
Comment on attachment 674948 [details]
Pointer https://github.com/mozilla-b2g/gaia/pull/5971

looks good now
Attachment #674948 - Flags: review?(dflanagan) → review+
Comment on attachment 674948 [details]
Pointer https://github.com/mozilla-b2g/gaia/pull/5971

a=me because this is a small js change for a big ugly issue but you may want to ask blocking-basecamp? next time :)
Attachment #674948 - Flags: approval-gaia-master?(21) → approval-gaia-master+
https://github.com/mozilla-b2g/gaia/pull/5971
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified on the 11/12 otoro us build.
Status: RESOLVED → VERIFIED
Verified on the 11/12 otoro us build.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: