Closed Bug 876785 Opened 13 years ago Closed 13 years ago

Task switcher goes fully black when there are no apps in the background

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 796241
1.1 QE3 (26jun)

People

(Reporter: diego, Assigned: alive)

Details

(Whiteboard: [leo-triage])

In v1.0.1 the screen just goes slightly darker. I checked the layers and it seems like the effect was achieved with a fullscreen black color layer which went semitransparent. This color layer now goes fully opaque. Note: This can be reproduced with both HwcComposer2D and GPU rendering.
If bug 796241 is not uplifted to leo, then we may need a different solution there
blocking-b2g: --- → leo?
Depends on: 796241
Whiteboard: [leo-triage]
NI? UX, was it intended this way to have a non-transparent black layer when doing task switch?
Flags: needinfo?(firefoxos-ux-bugzilla)
BTW, I recalled that I suggested: show 'No running apps' or message like that in the semi-transparent overlay but being rejected.
I'd be happy with just going back to graying out the screen. This black screen could easily trick the user into thinking they locked the phone.
Can we confirm the spec here and what expected behaviour is?
Flags: needinfo?(swilkes)
Assigning to Patryk (who can reassign as appropriate) to address the question in comment 3 on the non-transparent black layer.
Flags: needinfo?(swilkes)
Flags: needinfo?(padamczyk)
Flags: needinfo?(firefoxos-ux-bugzilla)
I believe we are using black as having a translucent wallpaper background is too costly CPU wise? Correct? I believe the clearest thing we can do is have some text at 2.1rem #FFFFFF font weight = 300 state: "You don't have any open applications." or "No recent open apps" I feel otherwise its not going to be clear to the user what is happening, especially since its a hidden function. For v.1.2 we'll have media controls accessible outside of the music application, so there will always be some sort of app running in the background, or at least there is an option for this.
Flags: needinfo?(padamczyk)
(In reply to Patryk Adamczyk [:patryk] UX from comment #8) > I believe we are using black as having a translucent wallpaper background is > too costly CPU wise? Correct? > > I believe the clearest thing we can do is have some text at 2.1rem #FFFFFF > font weight = 300 state: > > "You don't have any open applications." or "No recent open apps" > > I feel otherwise its not going to be clear to the user what is happening, > especially since its a hidden function. > > For v.1.2 we'll have media controls accessible outside of the music > application, so there will always be some sort of app running in the > background, or at least there is an option for this. Still don't think so. The stuff you mentioning smells like a music widget on homescreen or else where. Android doesn't show this kind of service at task manager. Is v1.2 design finalized? This definitely needs big change -- irrelavant to music app or media apps only.
blocking-b2g: leo? → leo+
Target Milestone: --- → 1.1 QE3
Assignee: nobody → alive
This bug and bug 796241 are pretty much tracking the same thing here. I'm duping this.
Status: NEW → RESOLVED
blocking-b2g: leo+ → ---
Closed: 13 years ago
No longer depends on: 796241
Resolution: --- → DUPLICATE
(In reply to Jason Smith [:jsmith] from comment #10) > This bug and bug 796241 are pretty much tracking the same thing here. I'm > duping this. > > *** This bug has been marked as a duplicate of bug 796241 *** I agree they're related but quite the same. Granted, if the task switcher didn't open as described in bug 796241 this bug wouldn't exist. However this bug is leo+ while bug 796241 is not. And there are ways to solve this without solving bug 796241, like displaying a "no apps loaded" text or graying out the screen.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
(In reply to Diego Wilson [:diego] from comment #11) > (In reply to Jason Smith [:jsmith] from comment #10) > > This bug and bug 796241 are pretty much tracking the same thing here. I'm > > duping this. > > > > *** This bug has been marked as a duplicate of bug 796241 *** > > I agree they're related but quite the same. Granted, if the task switcher > didn't open as described in bug 796241 this bug wouldn't exist. However > this bug is leo+ while bug 796241 is not. And there are ways to solve this > without solving bug 796241, like displaying a "no apps loaded" text or > graying out the screen. See https://bugzilla.mozilla.org/show_bug.cgi?id=796241#c8. Titles might be not exactly the same, but the solutions as seen by the comment are tracking a similar path. On that note, I'm reduping. Just because one of three bugs became leo+ doesn't make the argument that one bug should stay open over another. A dupe is a dupe.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → DUPLICATE
Also - if we followed comment 11 in the first place we would have kept bug 796241 closed as invalid. But that's not true here - it was reopened to address user feedback, which is exactly what this bug is talking about.
I see. Leo, Given this bug was marked as leo+ while bug 796241 was marked as a polish bug and now they're duped, do you want to keep bug 796241 as a it is?
Flags: needinfo?(leo.bugzilla.gaia)
Flags: needinfo?(leo.bugzilla.gaia)
You need to log in before you can comment on or make changes to this bug.