723714 - Running GIS Cloud native app to switch map listing causes it to become completely blank and fail to switch to the new map listing

Status: RESOLVED INVALID

(Firefox Graveyard :: Webapp Runtime, defect)

Description

[Jason Smith [:jsmith]]

Attachment: GIS Cloud Blank Native App

Steps:

1. Install the Apps Runtime Extension v0.51 on Firefox 10
2. Go to apps-preview.mozilla.org
3. Install the GIS Cloud App natively
4. Run the GIS Cloud App natively
5. Switch to a new map listing (example: Click "2" under "Maps")

Expected:

The app should load the next map listing selected.

Actual:

The native app becomes blank (see screenshot) and then continues to show the same map listing that was shown before. In other words, the map listing selected was not loaded.

Additional Notes:

Issue is not a website-specific issue, as this does not happen with the website on Firefox 10 and Chrome. Additionally, issue does not show up on web version of the app when ran through the dashboard.

Comment 1

[Jason Smith [:jsmith]]

Issue also occurs with The Times Crossword app.

Comment 2

[Bill Walker [:bwalker] [@wfwalker]]

I wonder if this might be related to bug 719175

Comment 3

[Jason Smith [:jsmith]]

Also occurs on the Lucidchart app.

Comment 4

[Jason Smith [:jsmith]]

I've seen this happen on the web version of "The Times Crossword" app in the past, although I'm not getting a reproduction now. Might be a good idea to fix this for MWC, since the possibility of this happening during a MWC demo on the web could be risky.

Comment 5

[Jason Smith [:jsmith]]

Switching to Non-mwc blocker until I start seeing this issue happen more frequently.

Comment 6

[Jason Smith [:jsmith]]

Definitely mozilla-central worthy.

Comment 7

[Jason Smith [:jsmith]]

Why was this migrated back to web apps general? Why was it removed from the tracking bug? This issue has to do "using apps" portion of the native apps experience, which is a requirement for the web apps integration into desktop feature.

Comment 8

[Jason Smith [:jsmith]]

Looks like this does not happen on OS X 10.6 on the new desktop runtime implementation. Will need to test with Win 7 as well. If it passes on Win 7, this bug then needs to be closed out as a Works for Me.

Comment 9

[Jason Smith [:jsmith]]

Tested on Win 7 64-bit and OS X 10.6.8. Did not get a reproduction of this issue on the new implementation. This bug is no longer valid.