Home → Bug Reports →

Firefox dialog leave page warning not appearing in Firefox for 6.10.7

• Edit

leslieg

15 Feb, 2012 06:41 PM

We are in a training class for our users and one of them lost the content on a new page she was working on. She's using Firefox 3.6.25 on a Mac. I witnessed this occurring several times for her. We are on Cascade 6.10.7. She's very irritated that she lost a lot of information. I haven't asked her to clear her cache because this isn't a viable solution in any case.

I noticed someone else submitted a ticket on this site but it was closed, apparently without resolution.

http://help.hannonhill.com/discussions/bug-reports/158-are-you-sure...

1. 1 Posted by leslieg on 15 Feb, 2012 06:44 PM

   

   would be good to add Timothy Gilman to this ticket.

   • Edit

2. 2 Posted by Bradley Wagner on 15 Feb, 2012 06:46 PM

   

   Hi Leslie, is there any way for us to find out if your user is getting any JavaScript errors n her browser when this happens?

   That seemed to be what was happening to Timothy, but the issue went away rather mysteriously when he cleared his browser caches.

   Timothy, have you had any issues with this feature since then?

   • Edit

3. 3 Posted by leslieg on 15 Feb, 2012 07:01 PM

   

   Unfortunately, I couldn't bc she shut down the computer and now I can't get
   into it. Turns out she was actually using windows. It was using bootcamp
   or something so using Mac machine but Windows OS.

   Did Tim have to clear cache once and never again or repeatedly?

   • Edit

4. 4 Posted by leslieg on 15 Feb, 2012 07:44 PM

   

   I logged onto another computer in the same training room and had no
   problem. I was on a similar machine (Mac) and the Firefox version was
   almost the same 3.6.24

   • Edit

5. 5 Posted by Timothy Gilman on 16 Feb, 2012 11:57 PM

   

   Each computer that had the issue required us to clear the cache for the browsers on that computer. But once we cleared the caches on a computer, then that computer worked fine from that point on.

   • Edit

6. 6 Posted by leslieg on 17 Feb, 2012 12:11 AM

   

   Thanks Tim - I didn't realize it was a one time fix.

   Sent from my iPhone

   • Edit

7. 7 Posted by Bradley Wagner on 17 Feb, 2012 12:30 AM

   

   Did either of you recently upgrade to a 6.8.x or 6.10.x version from a 6.7.x version of Cascade?

   I think I've discovered a possible issue that could occur for a user that had been using Cascade 6.7.x prior to the system getting upgraded to 6.8.x or 6.10.x.

   • Edit

8. 8 Posted by Timothy Gilman on 17 Feb, 2012 12:43 AM

   

   Yes. We were on 6.7.x (6.7.4 or 6.7.6) and upgraded to 6.10.7. It was after that when we encountered the problem.

   • Edit

9. 9 Posted by Bradley Wagner on 17 Feb, 2012 12:45 AM

   

   Thanks for confirming!

   • Edit

10. 10 Posted by leslieg on 17 Feb, 2012 04:46 PM

    

    Yes, I think so. I think we were on 6.7.3 and upgraded to 6.10.7. This was our development system. Our production system is currently at 6.10.3 and I don't remember what the last version was. I'm thinking it was also 6.7.3.

    • Edit

11. 11 Posted by leslieg on 17 Feb, 2012 04:48 PM

    

    Is there anything we should do differently to prevent this? Any idea how widespread the problem would be? ie. how rare this issue would be for firefox users? Trying to figure out if its something we want to communicate to folks...

    • Edit

12. 12 Posted by Bradley Wagner on 17 Feb, 2012 05:51 PM

    

    I've identified an issue (CSI-320) with the upgrade from 6.7.x to either 6.8.x or 6.10.x where the browser is allowed to use an older cached version of the JavaScript that handles these warnings and is resulting in JS errors in the edit screen.

    To verify that you're running into this issue:

    • load the edit screen on an affected browser
    • open the JavaScript console
    • look for any errors related to the editwarn.js file that Cascade uses

    If you do see errors, it is likely the same issue. If not, it's possibly something different, so please post here with any details.

    The only workarounds right now are to clear the browser cache clear or to slightly change the URL for Cascade to force the browser to fetch the JavaScript again.

    We'll definitely look to address CSI-320 in a near-term maintenance release.

    Sorry for the trouble.

    • Edit

13. Tim closed this discussion on 13 Mar, 2012 09:01 PM.