Closed
Bug 803447
Opened 12 years ago
Closed 12 years ago
During app-to-app switching, if the switching canceled by the user, or one of the app crashes, the transition will never complete
Categories
(Firefox OS Graveyard :: Gaia, defect, P1)
Tracking
(blocking-basecamp:+)
VERIFIED
FIXED
blocking-basecamp | + |
People
(Reporter: mossop, Assigned: timdream)
References
Details
(Keywords: b2g-testdriver, unagi)
Attachments
(2 files)
Apparently there is a way to bring up preview cards of running apps (like in WebOS). I don't know how you do it, but somehow I managed it and then somehow they got stuck there and now I am panning around in the homescreen despite these cards hovering over the top. They are just visual, tapping acts as if they weren't there.
Reporter | ||
Comment 1•12 years ago
|
||
Only the notification bar appears over the top of them and it seems I can't get rid of them without restarting the phone.
Comment 2•12 years ago
|
||
This sounds like a usability issue.
+Josh/Patryk for comment
Dave is having a hard time figuring out he invoked the task manager, which means he also had a hard time figuring out how to close it.
Updated•12 years ago
|
blocking-basecamp: --- → ?
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•12 years ago
|
||
I don't think this is a duplicate, but 796238 talks about being able to interact with the task manager, but in my case I couldn't.
Reporter | ||
Comment 5•12 years ago
|
||
Now that I've learnt how to open the task switcher I'm even more sure this isn't a dupe
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 6•12 years ago
|
||
It sounds like Dave encountered a bug. Normally users can easily exit the mode by 1.) selecting a card, or 2.) pressing the Home button. I don't think there's a usability issue here.
Comment 7•12 years ago
|
||
I'm not entirely convinced this isn't a dupe, but it is bad enough to block because it prevents you using the task switcher properly.
blocking-basecamp: ? → +
Reporter | ||
Comment 8•12 years ago
|
||
Saw this again today and here is a screenshot. I think when its in this state as far as the phone is concerned the task manager is closed, it just left behind the painted apps somehow.
You'll note that unlike when using the task manager normally the background isn't dimmed. I can also press where the big white box is that represents a running app and that tap goes through and presses whatever is underneath it, so aside from visually this state doesn't affect operation of the phone. Heck I can even open the task manager in this state and it appears underneath the stuck apps, I can make use of it and close it and the stuck apps remain there.
Reporter | ||
Comment 9•12 years ago
|
||
When in this state opening apps shows them appear in the white box and then expand to fill the screen. Pressing home makes them shrink down to the size of the white box and then just go totally white.
I've noticed in some cases switching from one app to another will briefly show a task display like this so I wonder if it is something to do with that breaking?
Reporter | ||
Comment 10•12 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #9)
> When in this state opening apps shows them appear in the white box and then
> expand to fill the screen. Pressing home makes them shrink down to the size
> of the white box and then just go totally white.
I should note that once expanded the white box (and side of calculator) appears over the top of the app, but again doesn't interfere with the operation of the app.
Z-ordering issue perhaps?
Comment 12•12 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #9)
> I've noticed in some cases switching from one app to another will briefly
> show a task display like this so I wonder if it is something to do with that
> breaking?
I think you are talking about web activity which disposition is 'window'.
But I couldn't reach your state by any operation, could you please provide more clear Steps to Reproduce? Much thanks.
Comment 13•12 years ago
|
||
(In reply to Chris Jones [:cjones] [:warhammer] from comment #11)
> Z-ordering issue perhaps?
From the images Dave attached, the semitransparent overlay and app name is hidden, only the images are shown.
And he said he could play the homescreen as if the images are not there.
I guess this is a rendering issue. But I never saw this.
Assignee | ||
Comment 14•12 years ago
|
||
Update the title to explain what's going on, and take the bug.
Assignee: nobody → timdream+bugs
Summary: Permanent overlay of running apps → During app-to-app switching, if one of the app crashes, the transition will never complete
Assignee | ||
Comment 15•12 years ago
|
||
Ah, I've already took the issue :-/
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 16•12 years ago
|
||
Sorry, my bad, unrelated
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 17•12 years ago
|
||
Blocking retriage: Not blocking on single-user-reproducible issues. This seems bad, but no other reports of this have come in. We'll reconsider blocking if/when that happens.
blocking-basecamp: + → -
Comment 18•12 years ago
|
||
Assignee | ||
Comment 21•12 years ago
|
||
I am worry that starting fixing this bug before https://github.com/mozilla-b2g/gaia/pull/5888 is merged will break it. So I will wait for it while working on a fix on top of those commits.
Depends on: 802647
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P1
Assignee | ||
Updated•12 years ago
|
Summary: During app-to-app switching, if one of the app crashes, the transition will never complete → During app-to-app switching, if the switching canceled by the user, or one of the app crashes, the transition will never complete
Assignee | ||
Comment 23•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/pull/6180
This patch attempts to fix the app-to-app transition by changing the underlining method we do transitions, instead of delivering a fix that pile things on the top of the current code. (code removed > code added!!)
Currently, depend on the unpaint state, Window manager might transition the frame or the sprite; maintain the code to control the state of both of them, especially and handling interruptions is tough. This patch fix that by removing the use of sprites (both #windowSprite and .windowSprite) and always transition on the actual frame.
For unpainted frame, we will set the background of the frame to the screenshot blob stored in the database; since an unpainted frame is transparent, we ended up transition the screenshot (the desired effect). As soon as the firstpaint happens, we reset the background and continue the transition with actual frame content.
The only intend impact to the transition animation is the crossfade between frame content and the screenshot -- that won't happen anymore; it would just suddenly switch when firstpaint happens. Some app flashes white briefly during the switching between two because firstpaint doesn't guarantee the app is loaded -- that can be improved on individual apps on bug follows.
Attachment #678515 -
Flags: review?(21)
Attachment #678515 -
Flags: review?(21) → review+
Assignee | ||
Comment 24•12 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•