slisir wrote:However if you disable JavaScript only on that site, it's not disabling the actual function of Personas, right?
Well, effectively it is. At this point in time there is only one website that will 'react', so break the JS link and for all intents and purposes, you have disabled the functionality. Yes, other sites could, and may well offer, the same but they would have to get through the security whitelist first.
As for the everything I tried, I was referring to settings we can set within the prefcalls.js or firefox.js that normally we can use to disable or lock a feature in FF. Unless there is a setting I missed to do this.
Playing around with the app itself is possibly unwise. Especially as any update will wipe out any changes.
I saw the option using userChrome, but problem with the userChrome.js is that the user still has rights to change that setting, even if the user doesn't have admin rights. So I was looking for an alternative from a standpoint of doing this for 200+ people and locking it so they can't edit it and turn it back on, it's also a pain to create/copy this file to each persons mozilla profile directory.
Hmm, 200+, eh? Profile prefs.js would do it (in about 4 lines) as would a quick extension. You could even try a fake lightweighttheme-header and footer in the profile (they are .jpg, so put in a blank.jpg, rename and delete file extension) and set to read only - but that, if it worked, would only stop install, not js mouseover on the site.
Either way, tough call for 200+. Block site in hosts?
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.