After Update 36 Optins Tab's are blank sometimes, WTH?
Toady Firefox Updated to v36 & toady Tabs on Options started to behave strangely, one time its General Tab that is Blank then i switch between Tabs & close option & reopen & next time its Privacy, all Tabs Randomly, WTH is going on? is it a temporary thing?
Sugram22 மூலமாக திருத்தப்பட்டது
தீர்வு தேர்ந்தெடுக்கப்பட்டது
it seems clean reinstall fixed the issue, it seems so for new, last time i did that i did not know there are 2 locations for profile folder & that both need to be deleted, if the issue returns i will write again, i had few other issues to & that's why i did clean reinstall
Read this answer in context 👍 1All Replies (4)
philipp said
the browser.preferences.inContent preference has nothing to do with tracking or ghostery - it changes how the firefox options panel is displayed (and incidentally that is in a way where ghostery doesn't interfere by showing a blank screen) - so just try it out...
OK i'l try
philipp said
the browser.preferences.inContent preference has nothing to do with tracking or ghostery - it changes how the firefox options panel is displayed (and incidentally that is in a way where ghostery doesn't interfere by showing a blank screen) - so just try it out...
i just need to change browser.preferences.inContent false to true?
EDIT: just tried it, after browser restart it resets to false :(
Sugram22 மூலமாக திருத்தப்பட்டது
philipp said
the browser.preferences.inContent preference has nothing to do with tracking or ghostery - it changes how the firefox options panel is displayed (and incidentally that is in a way where ghostery doesn't interfere by showing a blank screen) - so just try it out...
another issue with it, same settings can't be changed after doing that, if options wont open in that small widow, i can change them, but when i open again the settings are reset, i changed option & choice no proxy & that is set to default to, half the settings are set to default once i close the settings tab
Sugram22 மூலமாக திருத்தப்பட்டது
i was told it is firefox bug & that it will be fixed with 36.0.1 update, but it still exists after update