Closed
Bug 810449
Opened 12 years ago
Closed 12 years ago
[Trusted UI] Accessing an existing app process using a trusted UI through the task switcher opens up a blank homescreen
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-basecamp:+)
VERIFIED
FIXED
blocking-basecamp | + |
People
(Reporter: jsmith, Assigned: alberto.pastor)
References
Details
Attachments
(1 file)
216.08 KB,
image/png
|
Details |
Build: Device - Unagi Hashes <project name="gaia" path="gaia" remote="b2g" revision="319123f39aacfc98387390e1f173035f1870bacd"/> <project name="releases-mozilla-aurora" path="gecko" remote="mozilla" revision="48017631bc649ce43791db461d3a549ec51a27e3"/> Steps: 1. Launch trusted UI with mozPay 2. Hit the home button 3. Open the task switcher 4. Go back to the process using the trusted UI currently Expected: The trusted UI for that process should open on top of the homescreen. Actual: A blank homescreen instead. The work-around is to hit the home button to get out of this state.
Reporter | ||
Updated•12 years ago
|
Blocks: basecamp-id, basecamp-payments
Reporter | ||
Comment 1•12 years ago
|
||
Btw - there is weird behavior that can happen if the work-around is done, as I hit a case with trusted UI ending up on top of another app.
Reporter | ||
Updated•12 years ago
|
Summary: [Trusted UI] Accessing an existing app process using a trusted UI opens up a blank homescreen → [Trusted UI] Accessing an existing app process through the task switcher using a trusted UI opens up a blank homescreen
Reporter | ||
Updated•12 years ago
|
Summary: [Trusted UI] Accessing an existing app process through the task switcher using a trusted UI opens up a blank homescreen → [Trusted UI] Accessing an existing app process using a trusted UI through the task switcher opens up a blank homescreen
Reporter | ||
Updated•12 years ago
|
No longer blocks: basecamp-payments, basecamp-id
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P1
Comment 2•12 years ago
|
||
blocking+ -- can't land on a blank screen without direction.
Priority: P1 → P2
Comment 3•12 years ago
|
||
It feels like the homescreen does not have receive it's iframe.setVisible call. Assigning to Tim, feel free to re-assign if you're too overloaded.
Assignee: nobody → timdream+bugs
Comment 4•12 years ago
|
||
It seems that Alberto already fixed this on https://github.com/albertopq/gaia/commit/a033d4a2da61e412cb032dd32648b4e9acef7c09 Re-assigning to him.
Assignee: timdream+bugs → alberto.pastor
Comment 5•12 years ago
|
||
I've never tried to invoke Trusted UI, and would like to know how to trigger it for testing!
Comment 6•12 years ago
|
||
(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) from comment #5) > I've never tried to invoke Trusted UI, and would like to know how to trigger > it for testing! UITest -> navigator.mozPay test -> PMPP
Comment 7•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/c07be76497a9231b97faf260089c2f4aa3b91d84
Status: NEW → RESOLVED
blocking-basecamp: + → ?
Closed: 12 years ago
Priority: P2 → --
Resolution: --- → FIXED
Comment 8•12 years ago
|
||
Sorry, I didn't mean to set the blocking-basecamp flag to '?'. I am afraid that I can't set it back to '+'.
Updated•12 years ago
|
blocking-basecamp: ? → +
Reporter | ||
Comment 9•12 years ago
|
||
Verified on 11/16 build.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•