Re: SM is not accepted by Chase.com - again!
cmcadams wrote:
David E. Ross wrote:
On 3/31/2018 11:23 AM, EE wrote:
cmcadams wrote:
Trying a user.js didn't work.
prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.
If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config. This includes errors in syntax in
the setting, and also settings that are simply not recognized. The
format for entries in user.js is the same as that for prefs.js.
To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running. Note
that the semicolon (;) is required.
Then, launch SeaMonkey and enter about:config in the address area (URI
bar). You should see
00_user.js.loaded user set string yes
if the entire user.js file was okay. If there was a problem, you will
instead see
00_user.js.loaded user set string user.js load failed
This also works with Thunderbird and should work (but I have not tested
it) with Firefox.
Thank you, I've saved this.
Does anyone know for certain which Windows programs will work to edit
and save SM config files? And with what settings? Are they ASCII? ANSI?
I figured that's where I went wrong, trying to edit prefs.js.
Use an ordinary text editor, not a word processor.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM is not accepted by Chase.com - again!
On 4/1/2018 at 1:05 AM, cmcadams created this epitome of digital genius:
David E. Ross wrote:
On 3/31/2018 6:49 PM, cmcadams wrote:
David E. Ross wrote:
On 3/31/2018 11:23 AM, EE wrote:
cmcadams wrote:
Trying a user.js didn't work.
prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I
suppose.
If an entry into user.js is not recognized by SeaMonkey as being
valid,
it will not appear in about:config. This includes errors in syntax in
the setting, and also settings that are simply not recognized. The
format for entries in user.js is the same as that for prefs.js.
To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running. Note
that the semicolon (;) is required.
Then, launch SeaMonkey and enter about:config in the address area (URI
bar). You should see
00_user.js.loaded user set string yes
if the entire user.js file was okay. If there was a problem, you will
instead see
00_user.js.loaded user set string user.js load failed
This also works with Thunderbird and should work (but I have not tested
it) with Firefox.
Thank you, I've saved this.
Does anyone know for certain which Windows programs will work to edit
and save SM
config files? And with what settings? Are they ASCII? ANSI? I figured
that's where I
went wrong, trying to edit prefs.js.
The prefs.js file is plain ASCII text. Unlike Daniel, I prefer always
using Wordpad. I even set Wordpad as the default appplication for when
I select "Edit" on the context menu for all .js files.
So at least there's no need to worry about that. I can just right-click
"Open with" and use Notepad or Wordpad depending on size.
If using Wordpad just make sure that you Save As Text. There are other
formats WP can use that will totally screw up your file.
--
Ed Mullen
https://edmullen.net/
Bureaucracy: a method of turning energy into solid waste.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM is not accepted by Chase.com - again!
On 3/31/2018 at 2:38 PM, cmcadams created this epitome of digital genius: WaltS48 wrote: On 3/30/18 10:25 PM, cmcadams wrote: Ed Mullen wrote: On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of digital genius: As of about a week ago, when I log into my Chase accounts account using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following page: https://m.chase.com/secure.html?newstoken=false=https%3A%2F%2Fm.chase.com%2Findex.html=success
Re: SM is not accepted by Chase.com - again!
cmcadams wrote on 01/04/18 15:27:
David E. Ross wrote:
On 3/31/2018 11:23 AM, EE wrote:
cmcadams wrote:
Trying a user.js didn't work.
prefs.js didn't wish to be changed...tried both Windows 7 Notepad and
DOS Edit, but evidently didn't know the right save options, because
after running SM the new entry disappeared. Rejected by SM, I suppose.
If an entry into user.js is not recognized by SeaMonkey as being valid,
it will not appear in about:config. This includes errors in syntax in
the setting, and also settings that are simply not recognized. The
format for entries in user.js is the same as that for prefs.js.
To check whether SeaMonkey loaded all of user.js into prefs.js
successfully, insert
user_pref("00_user.js.loaded", "user.js load failed");
as the very first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the very last line of user.js, all with SeaMonkey not running. Note
that the semicolon (;) is required.
Then, launch SeaMonkey and enter about:config in the address area (URI
bar). You should see
00_user.js.loaded user set string yes
if the entire user.js file was okay. If there was a problem, you will
instead see
00_user.js.loaded user set string user.js load failed
This also works with Thunderbird and should work (but I have not tested
it) with Firefox.
This works, I am duly amazed.
With both Notepad and (after toggling value to null) in Wordpad, no
problems.
Thank you very much.
Alls well that ends well!! Good to hear!
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
SeaMonkey/2.49.1 Build identifier: 20171016030418
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
SeaMonkey/2.49.1 Build identifier: 20171015235623
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM video problems continue - will they ever end!?
IRRITATING SPAMMER wrote: null wrote: IRRITATING SPAMMER wrote: null wrote: Have had increasing problems playing video in SM for a long time now. Getting the latest SM version doesn't help. Seems it all stems from ongoing, behind-the-scenes jostling between flashplayer, WEBM and the HTML5 player. Currently I can't play anything on Facebook or Instagram, and many news sites have video that won't play. The latest nonsense on many news sites is a message saying "This video could not be loaded - crossdomain access denied". No idea exactly what that implies. Are other SM users having these sort of problems? I was googling around and found something for "Cannot load M3U8: crossdomain access denied" (not that the solution made sense to me) so I have to ask: did you change the error-message before posting it here? I think that "M3U8" was part of it, at least on some occasions, but the key part is the reference to "crossdomain access". Some of the people who had that error were using something called PleX and had to change a setting, this seemed to be independent of the actual browser used. If you saw M3U8, that appears to be just as important as the "crossdomain access denied". Google the entire string above - including the double quotes - and see what applies. Whether you google "crossdomain access denied" or "Cannot load M3U8: crossdomain access denied", you get essentially the same list of citations, none of which, I might add, are particularly helpful. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM is not accepted by Chase.com - again!
Marisa Ciceran wrote on 30-03-18 16:45: As of about a week ago, when I log into my Chase accounts account using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the following page: https://m.chase.com/secure.html?newstoken=false=https%3A%2F%2Fm.chase.com%2Findex.html=success
