On 10/29/2016 7:39 PM, JAS wrote: > J. Weaver Jr. wrote: > >> >> In a browser page address bar, type "about:config" (without the quotes). >> >> Anywhere in the body of the page, right click, select "New" and "String". >> >> At the "Enter the preference name" prompt, type >> "general.useragent.override.chase.com" (without the quotes). >> >> At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0) >> Gecko/20100101 Firefox/43.0" (again, without the quotes). >> >> Many other user agent strings will also work, but that one's working for >> me. -JW > I thought that the general.useragent.override did not work anymore? At > least it does not for me. >
When I use the PrefBar extension to spoof a different browser, the preference variable general.useragent.override -- the same one you cite -- is what gets set. I tested it at two Web pages, and it does work. The two test pages are: * My own <http://www.rossde.com/internet/intr_gloss.shtml>. You can see your own UA string under the entry for "UA". Note that two UA strings are shown there: my default UA string back in 2014 (when I last updated the page) and any visitor's current UA string. * Panopticlick at <https://panopticlick.eff.org/>. After Panopticlick did its analysis, I had to ask it for details. The UA string appeared near the bottom of the list of details. If you manually edit prefs.js while SeaMonkey is an active application (even if it is idle) rather than using about:config, it will not be effective. The prefs.js file on disc is read when SeaMonkey is launched. Thereafter, only the in-memory copy is used. Furthermore, the in-memory copy is then written over the disc file when SeaMonkey is terminated. In other words, DO NOT MANUALLY EDIT prefs.js. (There is an exception when moving the location of a SeaMonkey profile, either to a different disc location or to a different computer.) My preferred methods of changing preferences are, from most to least preferred: * [Edit > Preferences] on the SeaMonkey menu bar * An extension, especially PrefBar * editing the file user.js, which requires SeaMonkey to be terminated and then re-launched to become effective * about:config (generally only for testing a preference change) The above is based on my experience with a major computer system used by the U.S. military to operate its space satellites. Part of my task was to train U.S. Air Force officers on how to use the system. I always emphasized that changes to system controls were best done by using the available user-oriented applications for that purpose instead of trying to tweak the controls via the database system. That ensured all subsidiary changes related to the primary change -- many of which were not obvious -- were also done because they were built into the user-oriented applications. The last time I edited the prefs.js file was in 2013, when my Windows XP PC died and I had to rehost SeaMonkey on a Windows 7 PC. Fortunately, the hard drive containing my data (including my SeaMonkey profiles) could be read by the new PC. -- David E. Ross Donald Trump claims everyone likes him. Does that include his ex-wives? How about the students who discovered that their education at Trump University was worthless? And how about the contractors, suppliers, and employees he stiffed in his several bankruptcies? _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
