![]() Obviously this is annoying and I would like to get FF to work properly. I've been running this for several years so it's not something I recently installed and started causing the problem, but they do make frequent updates. I've also verified that my settings for restoring tabs is set to restore the session.Īlso I the noscript addon which might be relevant since this is a script. I've saved a copy of the current sessionrestore.js file since it gets over written when I open FF so that I can try and debug this problem. No surprising, if I chande 'Char 11' to ' " I get a different error. I opened the sessionrestore.js file with notepad and can see the tab info that needs to be restored. Source: Microsoft JScript compliation error The session restore feature in Firefox has been enhanced a while back to let users select the pages which they wish to restore. I've gone directly to the sessionrestore.js file and tried to open FF from there, but I get an error. Append -restore-last-session to the end of the target field and make sure there is a space between it and the preceding character. Took the recovery.js file, made a copy of it in my non-Firefox folder and renamed the copy sessionstore.js. I renamed the current sessionstore.js to sessionstoreOLD.js. Do not close Firefox Make a copy of the folder: C: Users. Upon opening FF after a crash, I just get the start up page, it no longer asks me if I want to restore the tabs I had open.Īfter FF is open the sessionrestore.js file is reset and I can not restore the previously open tabs. Right-click on the Chrome icon, then right-click on the Google Chrome name in the jumplist, and then on Properties if it is pinned to the taskbar. I moved the sessionstore-backups folder to a non-Firefox folder. If your tabs disappeared and the previous session is not restored: 1. I'm now using FF 12 and the session restore no longer works after crashes. Firefox used to restore my browser session after a crash. The session-restore feature in Mozilla Firefox before 28.0 and SeaMonkey before 2.25 does not consider the Content Security Policy of a data: URL, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via a crafted document that is accessed after a browser restart.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |