Şu anda bakım nedeniyle sitemiz kısıtlı işlevsellik sunmaktadır. Mevcut makaleler sorununuzu çözmediyse ve bize soru sormak isterseniz Twitter’da @FirefoxSupport hesabından ve Reddit’teki /r/firefox subreddit'inden destek gönüllülerimize ulaşabilirsiniz.

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

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?

  • 1 yanıt
  • 2 kişi bu sorunu yaşıyor
  • 2 gösterim
  • Son yanıtı yazan: the-edmeister

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???

Tüm Yanıtlar (1)

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.