User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 Build ID: 20121128204232 Steps to reproduce: 1. Launch Unagi build 20130104070203 Version 18.0 2. Verify you have a working wireless or data connection. 3. Launch the Maps app. 4. Verify it loads as expected. 5. Tap the home button to go back to the Home Screen. 6. Go into options and turn any Wireless and Data connection OFF. 7. Go back into Maps and Deny GPS activation. 8. Move the map around with your finger and notice that the map cannot update because there is no internet or data connection to update new data. 9. You will see the map graphics become corrupted. Repro: 5/5 seen on multiple devices. Actual results: On a running Map app, if you remove any internet/data connection then try to use the Maps app again, you will see no message about not having any wireless/data connection but instead you will just get corrupted graphics when you move the map around. Expected results: It would seem to me that a (no internet/data connection) message should be seen before the user can access the map. Perhaps before the user even sees the GPS message, the app should check for internet/data access at this point.

I understand if there is nothing you can do here. I tested other apps and see the pre-cached information is shown but graphical corruption is something that no End User wants to see. It always looks bad when there is no message telling the user something is not working correctly and how to solve it.

I'm pretty sure this is a dupe of an existing bug we came across in tef? triage if someone knows what I'm talking about please close this out. Comment 1 seems incorrect, we can investigate graphic layer corruption here possibly locally - cc-ing Milan for further investigation.

I think the Comment 1 was meant to be "I know you can't update the map without the connection", and we all agree that it shouldn't draw the way it does?

I don't think this is a fx/b2g issue. This issue also appears on slow connections on Android/iOS. We (@Nokia) will also investigate further, but this should not be a blocker.

This should have been fixed with the latest package (januari 20). We cannot replicate anymore. Can you retest please?

(In reply to AndyT from comment #5) > This should have been fixed with the latest package (januari 20). We cannot > replicate anymore. Can you retest please? Closing per comment 5.

Verified as fixed in build 20130214070203 Version 18.0 Kernel Dec. 5th Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/d1288313218e Gaia 6544fdb8dddc56f1aefe94482402488c89eeec49