Status

The webapp runtime for Firefox, which comprises: the stub executable launcher (i.e. the binary and related files that Firefox creates for each webapp you install to your local computer) and the XUL shell (i.e. the XULRunner application that the launcher uses to load a webapp and provide it with native integration APIs). Note: bugs about Gecko's navigator.mozApps DOM API (i.e. the API that web pages use to request webapp installation) go in Core / DOM: Apps; bugs about Firefox's webapp installer (i.e. the feature that creates a launcher when the user approves an installation request) go in Firefox / Web Apps.

Security

(public)

User Story

Steps:
1. Install GIS Cloud (https://marketplace-dev.allizom.org/en-US/app/gis-cloud/?src=ss)
2. Launch that application
3. Go to sign in and select the facebook icon
4. After the facebook pop-up appears, close the parent window for GIS Cloud
Expected:
The GIS Cloud application and the facebook pop-up windows should close, given that the parent application has closed.
Actual:
The GIS Cloud application window closes, but the facebook pop-up does not (GIS Cloud process also remains running). Logging into facebook with that window open puts you onto a page of nothingness. Closing the facebook pop-up does shut down the application. This is differing behavior than how the persona pop-up works, where closing the parent window does close the persona pop-up correspondingly, which ends up ending the application process.
Additional Notes:
We need a resolution on how to do parent-child relationships for windows. What's the correct behavior and cases we need to handle?

(In reply to Edward Lee :Mardak from comment #1)
> For reference, Persona login closes itself when the main window is closed.
Ah okay. Testing in firefox, this is the same behavior firefox does, so I wonder if this is a problem or not. Should we do the same behavior for apps? Should it be the developer's job then to handle parent-child window relationships? Or should this be handled in our platform?