Closed Bug 1024472 Opened 10 years ago Closed 10 years ago

Closing an application-opened window does not return to the application

Categories

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

x86_64
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.0+, b2g-v1.4 unaffected, b2g-v2.0 verified, b2g-v2.1 verified, b2g-v2.2 verified)

VERIFIED FIXED
2.0 S4 (20june)
blocking-b2g 2.0+
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- verified
b2g-v2.1 --- verified
b2g-v2.2 --- verified

People

(Reporter: cwiiis, Assigned: alive)

References

Details

(Keywords: regression)

When an application opens a window, if that window is closed (presumably by window.close), you get returned to the home-screen instead of the application.

This happens when:

- Signing into Nokia Here maps
- Authenticating Evernote in Notes+

And a couple of other cases I forget right now.
blocking-b2g: 2.0? → 2.0+
Blocks: 1009271
Assignee: nobody → alive
QA Wanted to get STR using an actual test app to do a window against.
Keywords: qawanted
STR:

Prerequisite: A Nokia here.com account

1- Install and open Here maps
2- Choose the sign in option
3- Sign in and submit

Expected:
Window disappears and takes you back to the map application, logged in (works in 1.3 and 1.4)

Actual:
Window disappears and takes you back to the home screen. Re-opening Here maps logs in correctly.
QA Contact: pcheng
b2g-inbound Regression Window:

Last Working Environmental Variables:
Device: Buri
BuildID: 20140324205840
Gaia: befb78cce80144ba6c0783aefcf6b98439d0a8e9
Gecko: d70ec036c4f4
Version: 31.0a1 (Master)
Firmware Version: v1.2device.cfg

First Broken Environmental Variables:
Device: Buri
Build ID: 20140324215141
Gaia: 5c0b52751c7cf9f73d44126916a822baf65e2547
Gecko: 3a109b7a9f65
Version: 31.0a1 (Master) 
Firmware Version: v1.2device.cfg

Last Working Gaia / First Broken Gecko: Issue Does NOT reproduce
Gaia: befb78cce80144ba6c0783aefcf6b98439d0a8e9
Gecko: 3a109b7a9f65

Last Working Gecko / First Broken Gaia: Issue DOES reproduce
Gaia: 5c0b52751c7cf9f73d44126916a822baf65e2547
Gecko: d70ec036c4f4

Gaia Pushlog:
https://github.com/mozilla-b2g/gaia/compare/befb78cce80144ba6c0783aefcf6b98439d0a8e9...5c0b52751c7cf9f73d44126916a822baf65e2547
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Broken by bug 961800.
Blocks: 961800
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Bug 1021658 will fix this.
c.c. Etienne:
It seems use window.open is bad for web pages. In this case window.close will just kill the app window instance and back to homescreen, but if it's a sheet I am not sure what we want. Pref off child window should save us from this kind of issues.
Depends on: 1021658
closing since bug 1021658 landed, reopen if still reproduced.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S4 (20june)
Verified the issue is fixed on 2.2, 2.1 and 2.0 Flame 

After log in the user is redirected to the main page
Device: Flame 2.2 Master KK
BuildID: 20141104040207
Gaia: 3c50520982560ccba301474d1ac43706138fc851
Gecko: 54d05732f29b
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Device: Flame 2.1 KK
BuildID: 20141104001202
Gaia: 8b0cf889ae0d48a9eb7ecdcb9b67590de45cc5e5
Gecko: 388b03efe92d
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
    
Device: Flame 2.0 KK
BuildID: 20141104000201
Gaia: fe2167fa5314c7e71c143a590914cbf3771905a8
Gecko: 241e51806687
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 32.0 (2.0)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.