Re: prefs.js is not for user manipulation

2018-03-31 Thread WaltS48

On 3/30/18 4:26 PM, Felix Miata wrote:

WaltS48 composed on 2018-03-30 16:12 (UTC-0400):


I recenty edited a Thunderbird prefs.js file, not being 50% certain what
I was doing. It worked!

By all means, never follow manufacturer's instructions. You wouldn't want to
miss any opportunity to dig yourself into a hole you can't get out of.



Well, I wasn't adding anything to it, just changing 
"mail.preferences.inContent;true" to "false" for Thunderbird, because I 
couldn't see the Config Editor button when in Preferences.


Thought it might be a bug in TB on Linux only, but I later found out it 
was because I used the Unity Tweak tool to change the font text scaling 
factor to 1.25. It's now back to 1.00.


--
Best name ever! Cadet Bone Spurs
NRA = Newly Recruited Activists
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: prefs.js is not for user manipulation

2018-03-31 Thread Ed Mullen

On 3/30/2018 at 3:13 PM, Felix Miata created this epitome of digital genius:

Ed Mullen composed on 2018-03-30 11:32 (UTC-0400):


You simply need to use a different user agent string when going to
chase.com.  Add this to your prefs.js:



user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");


Never add anything to prefs.js if you're not 200% certain you know what you are
doing and how to undo the damage from a mistake. Either include it in user.js,
or include via about:config. User.js is an optional file that SM will only read,
never write.



"When you launch your Mozilla application, valid preferences you've 
added to the user.js file are automatically copied to the prefs.js file 
(located in the same profile folder) where all user-set preferences are 
stored. For this reason, you should make a backup copy of the prefs.js 
file before you create or edit the user.js file."


http://kb.mozillazine.org/User.js_file

--
Ed Mullen
https://edmullen.net/
"Computer Department:  Mistakes made while you wait."

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: prefs.js is not for user manipulation

2018-03-30 Thread Felix Miata
WaltS48 composed on 2018-03-30 16:12 (UTC-0400):

> I recenty edited a Thunderbird prefs.js file, not being 50% certain what 
> I was doing. It worked!

By all means, never follow manufacturer's instructions. You wouldn't want to
miss any opportunity to dig yourself into a hole you can't get out of.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: prefs.js is not for user manipulation

2018-03-30 Thread WaltS48

On 3/30/18 3:13 PM, Felix Miata wrote:

Ed Mullen composed on 2018-03-30 11:32 (UTC-0400):


You simply need to use a different user agent string when going to
chase.com.  Add this to your prefs.js:
user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");

Never add anything to prefs.js if you're not 200% certain you know what you are
doing and how to undo the damage from a mistake. Either include it in user.js,
or include via about:config. User.js is an optional file that SM will only read,
never write.



I recenty edited a Thunderbird prefs.js file, not being 50% certain what 
I was doing. It worked!


--
Best name ever! Cadet Bone Spurs
NRA = Newly Recruited Activists
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: prefs.js is not for user manipulation (was: SM is not accepted by Chase.com - again!)

2018-03-30 Thread Felix Miata
Ed Mullen composed on 2018-03-30 11:32 (UTC-0400):

> You simply need to use a different user agent string when going to 
> chase.com.  Add this to your prefs.js:

> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
> NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0");

Never add anything to prefs.js if you're not 200% certain you know what you are
doing and how to undo the damage from a mistake. Either include it in user.js,
or include via about:config. User.js is an optional file that SM will only read,
never write.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey