Sites not accepting Seamonkey

User Help for Seamonkey and Mozilla Suite
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: Sites not accepting Seamonkey

Post by frg »

> I wonder if imgur will work with the SM 2.57.x builds - I'm permanently switching to 2.57.x builds whether finalized or not for the remainder of 2020 and around the start of 2021

yes since last week. I ported the resizeObserver changes over. If I do them I usually start with 2.53 becuase that is where the users usually need it. While browsing generally works fine in 2.57 it it still a trainwreck with extensions and mail. Ok as a testbed in a vm or second desktop but not much more imho.

modules and service workers are still disabled in 2.53 because of known problems. Will be fixed in the next releases as time permits. If you encounter a website needing it you can enable temporarily. So far not many.

FRG
Anonymosity
Posts: 8779
Joined: May 7th, 2007, 12:07 pm

Re: Sites not accepting Seamonkey

Post by Anonymosity »

According to the producer of Pale Moon, this is a good image server:
https://imgbb.com/
User avatar
-Px-
Posts: 480
Joined: April 20th, 2011, 1:56 am

Re: Sites not accepting Seamonkey

Post by -Px- »

"Load more..." button on GitHub is broken now, loads empty page instead of loading hidden posts, error code 400 is produced in console
Example page for testing: https://github.com/hashicorp/terraform/issues/23679
User avatar
Frank Lion
Posts: 21173
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom
Contact:

Re: Sites not accepting Seamonkey

Post by Frank Lion »

-Px- wrote:"Load more..." button on GitHub is broken now, loads empty page instead of loading hidden posts, error code 400 is produced in console
Example page for testing: https://github.com/hashicorp/terraform/issues/23679
Can you explain where this 'Load More' button is on this page? -

Image
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.
User avatar
-Px-
Posts: 480
Joined: April 20th, 2011, 1:56 am

Re: Sites not accepting Seamonkey

Post by -Px- »

Frank Lion wrote: Can you explain where this 'Load More' button is on this page? -
Sure, it is in the middle of the page :)
Image
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: Sites not accepting Seamonkey

Post by therube »

This post, https://github.com/hashicorp/terraform/ ... -594353584, has a "Load more...", & yes, it does not work (in 2.49.5, & may very well not work in SeaMonkey 2.53.x ? nor possibly in Pale Moon?)

(Though in that thread, JustOff has an extension, github-wc-polyfill - who knows, that maybe could be adapted to SeaMonkey, maybe getting things to work - don't know?)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
User avatar
-Px-
Posts: 480
Joined: April 20th, 2011, 1:56 am

Re: Sites not accepting Seamonkey

Post by -Px- »

Aws seems updated their scripts some time ago, spot instances price page is not working in 2.53.4, error console gives this:

Code: Select all

[AwsUi]  Items contain a duplicated href: "http://documentation.aws.com". main.js:1:317334
[AwsUi]  Region alias "content" for "Flash" has been deprecated. Use "children" prop instead  main.js:1:317334
[AwsUi]  Region alias "text" for "Button" has been deprecated. Use "children" prop instead  main.js:1:317334
[AwsUi]  Region alias "text" for "ButtonDropdown" has been deprecated. Use "children" prop instead  main.js:1:317334
Error: Property "items" must be an array, was undefined (undefined)
Stack trace:
error@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:317917
R.validate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:16107
a/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:17276
_/p</h.prototype.componentDidUpdate/</<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:290906
_/p</h.prototype.componentDidUpdate/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:290585
e.__batchUpdate/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:28594
h/e.reactBatchUpdate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:288563
e.__batchUpdate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:28455
_/p</h.prototype.componentDidUpdate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:290299
is@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2437009
dl@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2454782
t.unstable_runWithPriority@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2474095
za@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398573
cl@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2451254
Qs@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2447408
Ya/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398864
t.unstable_runWithPriority@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2474095
za@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398573
Ya@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398809
Va@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398744
Ws@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2443998
enqueueSetState@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2402527
b.prototype.setState@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2348687
u</n.subscribe/this.unsubscribe<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:466387
h@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1819525
u/</<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4749425
dispatch@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1822690
k/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:84048
V/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4744788
r@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1565925
u@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1566075
o@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1565974
V@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4744744
j@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4743942
F@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4742829
l@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4743633
Y/<@https://cdn.assets.as2.amazonaws.com/awsc-global-nav.js?version=1.0.114:2:48686
r@https://cdn.assets.as2.amazonaws.com/awsc-global-nav.js?version=1.0.114:2:93408
  main.js:1:2435918
uncaught at  error@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:317917
R.validate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:16107
a/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:17276
_/p</h.prototype.componentDidUpdate/</<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:290906
_/p</h.prototype.componentDidUpdate/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:290585
e.__batchUpdate/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:28594
h/e.reactBatchUpdate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:288563
e.__batchUpdate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:28455
_/p</h.prototype.componentDidUpdate@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:290299
is@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2437009
dl@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2454782
t.unstable_runWithPriority@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2474095
za@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398573
cl@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2451254
Qs@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2447408
Ya/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398864
t.unstable_runWithPriority@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2474095
za@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398573
Ya@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398809
Va@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2398744
Ws@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2443998
enqueueSetState@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2402527
b.prototype.setState@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:2348687
u</n.subscribe/this.unsubscribe<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:466387
h@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1819525
u/</<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4749425
dispatch@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1822690
k/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:84048
V/<@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4744788
r@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1565925
u@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1566075
o@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:1565974
V@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4744744
j@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4743942
F@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4742829
l@https://d21c5hep65u2a6.cloudfront.net/js/main.js:1:4743633
Y/<@https://cdn.assets.as2.amazonaws.com/awsc-global-nav.js?version=1.0.114:2:48686
r@https://cdn.assets.as2.amazonaws.com/awsc-global-nav.js?version=1.0.114:2:93408
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: Sites not accepting Seamonkey

Post by frg »

Does not ring a bell. 2.53.5b1 is now available. You might try this one. Should be production quality.

Put some more fixes in 2.53.6b1 pre this week too but doubt it will help.

FRG
User avatar
-Px-
Posts: 480
Joined: April 20th, 2011, 1:56 am

Re: Sites not accepting Seamonkey

Post by -Px- »

frg wrote:Does not ring a bell. 2.53.5b1 is now available. You might try this one. Should be production quality.

Put some more fixes in 2.53.6b1 pre this week too but doubt it will help.

FRG
Tried today 2.53.6b1 and 2.57a1, no difference, the result/error is the same
User avatar
Frank Lion
Posts: 21173
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom
Contact:

Re: Sites not accepting Seamonkey

Post by Frank Lion »

Images in the Guardian newspaper don't seem to be showing up. Anyone else getting this problem?

https://i.guim.co.uk/img/media/1d597b14 ... 0c46b39c4b
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.
RDaneel
Posts: 603
Joined: January 19th, 2004, 2:43 pm
Location: Puget Sound, WA
Contact:

Re: Sites not accepting Seamonkey

Post by RDaneel »

WFM, using that link.
User avatar
Peter Creasey
Posts: 1340
Joined: October 26th, 2007, 2:32 pm
Location: Texas

Re: Sites not accepting Seamonkey

Post by Peter Creasey »

Frank, I get a weird cartoon.
. . . . . . . . . . Pete
User avatar
ndebord
Posts: 1122
Joined: December 7th, 2002, 9:53 am

Re: Sites not accepting Seamonkey

Post by ndebord »

Frank Lion wrote:Images in the Guardian newspaper don't seem to be showing up. Anyone else getting this problem?

https://i.guim.co.uk/img/media/1d597b14 ... 0c46b39c4b
Frank,

Nice narcissist image of DJT!

Nick
-N- Si vis pacem, para bellum
FrameWork, SeaMonkey(64-bit),Windows 10 Pro (X64- 21H2), WinPatrol, Malwarebytes & Panda Dome
User avatar
Frank Lion
Posts: 21173
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom
Contact:

Re: Sites not accepting Seamonkey

Post by Frank Lion »

All sorted, images now showing fine.
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.
User avatar
ndebord
Posts: 1122
Joined: December 7th, 2002, 9:53 am

Re: Sites not accepting Seamonkey

Post by ndebord »

frg wrote:Does not ring a bell. 2.53.5b1 is now available. You might try this one. Should be production quality.

Put some more fixes in 2.53.6b1 pre this week too but doubt it will help.

FRG
frg,

Tried 2.53.5b1 and it crashed my backup SM. Will post the error when I try it again. Ah, whatever the error was, it disappeared. This version works just fine on my setup when I tried again.
Nick
-N- Si vis pacem, para bellum
FrameWork, SeaMonkey(64-bit),Windows 10 Pro (X64- 21H2), WinPatrol, Malwarebytes & Panda Dome
Post Reply