This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

I was able to delete the NSPrivate Browsing file for earlier versions of FF but the components file is not in a "list form" for Version 4, so I can't delete the file. Does anyone have a solution please?

CATAB
CATAB
more options

I have been able to delete the NSPrivate Browsing file in previous versions of FF but when I open the components file in Version 4 it doesn't "List" the files which make up the components for me to delete, can anyone tell me how I can get rid of this stupid feature to stop it functioning please???

I have been able to delete the NSPrivate Browsing file in previous versions of FF but when I open the components file in Version 4 it doesn't "List" the files which make up the components for me to delete, can anyone tell me how I can get rid of this stupid feature to stop it functioning please???

All Replies (1)

the-edmeister
the-edmeister
  • Moderator
more options

The files that were in the \components\ folder in 3,6 and previous versions are in the Firefox 4 program files omni.jar file from what I have read and have seen. I don't recommend that you remove that file, but from what I have read WinRAR is probably the best program to use to open the omni.jar file. I have used WinRAR to extract the contents of that file to search for code for a different function, but I haven't tried repacking the omni.jar file. I have seen a few postings at MozillaZine where other users have had trouble getting Firefox to work after repacking the omni.jar file after modifying one of the internal files.