SM no longer works with Mastodon?

[Manuel Casal Lodeiro]

I've just found out that I can no longer see (or use) Mastodon instances
which have a recent software version (with the old ones there were no
problems at all). When visiting them I see nothing on the page and the
error console in Seamonkey throws this error:

> Error: SyntaxError: expected expression, got keyword 'import'
> Source File: https://mastodon.pub.solar/packs/assets/application-B7gmsjSL.js
> Line: 2, Column: 67330
> Source Code:
> zeEmoji:e}=await Y(async()=>{const{initializeEmoji:c}=await
> import("../emoji-index-j4Ni_llU.js");return{initializeEmoji:

Again, it seems like a Javascript issue.

Anyone here suffering the same problem?

Is there a way to avoid it, without having to drop Seamonkey as a browser?

Thanks.
--
< Manuel Casal Lodeiro, (a) «Casdeiro» >

Todo nuestro esfuerzo debe centrarse en evitar futuros infernales.

— Jorge Riechmann, "Gente que no quiere viajar a Marte"


---------------------------------------------------------------
[Mensagem escrita por um ser humano, sem nengumha maldita "IA"]

[Riccardo Mottola]

Manuel Casal Lodeiro wrote:
> I've just found out that I can no longer see (or use) Mastodon
> instances which have a recent software version (with the old ones
> there were no problems at all). When visiting them I see nothing on
> the page and the error console in Seamonkey throws this error:

I don't know if there is a way to avoid it, but I would also ask
software, especially if open, to support more browsers.

I just noticed that some very useful sites I use do not work with SM
anymore (beyound the cloudflare plague). Just because they are broken on
ArcticFox too, but used to work on SM (openstreet maps, windy)

Uphill battle, I know.

Riccardo

[Nuno Silva]

On 2026-01-26, Manuel Casal Lodeiro wrote:

> I've just found out that I can no longer see (or use) Mastodon
> instances which have a recent software version (with the old ones
> there were no problems at all). When visiting them I see nothing on
> the page and the error console in Seamonkey throws this error:
>
>> Error: SyntaxError: expected expression, got keyword 'import'
>> Source File: https://mastodon.pub.solar/packs/assets/application-B7gmsjSL.js
>> Line: 2, Column: 67330
>> Source Code:
>> zeEmoji:e}=await Y(async()=>{const{initializeEmoji:c}=await
>> import("../emoji-index-j4Ni_llU.js");return{initializeEmoji:
>
> Again, it seems like a Javascript issue.

Yes, upstream Mastodon started using dynamic imports. I get the same
issue on the instance I use mainly.

Others might still work if they're on older version branches.

*If you use Mastodon with an account*: If your instance works well with
some of these, you could give web clients a try if they work with
SeaMonkey themselves. But of course that requires trusting the web
client too.

*If you don't use with an account, and are merely reading the content*:

- Add .rss to the end of URLs to get Mastodon feeds (user posts, user
posts with replies, posts for a given hashtag) as an RSS feed.

- Some instances will allow getting the post as JSON if you add
.json. Not really practical for reading, but worth mentioning if
it. There are also (apparently much less common?) mods that also serve
text/plain for .txt.

- There is threadtree.xyz but it has a minimum thread size (10 posts, I
think). I think I also recall it not showing attached media.


- For the post itself, without the replies, you should be able to see
the post content and attached images and their alternate text in the
page meta tags (ctrl+I or View->Page Info, first tab ("General"))

- post text as og:description

- image(s) as og:image (URL)

- alt text as og:image:alt

(Why isn't this served as visible content if it's already being
injected in meta tags, well, yes, that's a great question...)

> Anyone here suffering the same problem?
>
> Is there a way to avoid it, without having to drop Seamonkey as a
> browser?

Support for dynamic imports will eventually land as part of the work
being done in the WIP branch (which isn't suitable to address these
issues because that work is being done without two other features that
are often required by the same sites that fail (IIRC optional chaining
and the new regexp syntax, but I could be misremembering) - thus it
being done on a separate branch).

--
Nuno Silva
(Please send your reply to the list)

[Pavel Boček]

IC, different issue then, but who knows. White page syndrome appears to plague many alternative browsers (incl. Palemoon and others based upon legacy Firefox), so far it has only been fixed in Basilisk via "polyfill hooks" functionality, as far as I found out.

Supposedly new javascript "functions" (I call it unnecessary crap though) which are not natively supported in these browsers. Could be the same with SM, it's all more or less based upon the same (or familiar) obsolete code which developers of each particular fork try to update with "modern" stuff, sometimes it goes without hassless, sometime it does not, and when it does not, these browsers than fall behind mainstream (chrome) plague in terms of "compatibility".

--
S uctivým pozdravem/best regards,

Pavel Boček
Jabber: Beh...@jabber.cz
+420 739 190 151
http://www.hwworld.cz (elektromontáže silnoproud/slaboproud, kondenzátory, aku/baterie, mikrospínače pro myši a klávesnice aj./capacitors etc.)
https://www.hardwareinsights.com (power supply reviews and more)
stickers-cz.com (nekonformní samolepky, placky)

---------- Původní e‑mail ----------
Od: Riccardo Mottola <riccardo...@libero.it>
Komu: Pavel Boček <bocek...@post.cz>
Datum: 4. 2. 2026 10:57:02
Předmět: Re: [support-seamonkey] SM no longer works with Mastodon?

Pavel Boček wrote:
> white page?

what do you mean, on openstreetmap? No, not white page, but the maps
does not laod anymore and the big area remains grey.

Just try:
https://www.openstreetmap.org/

Same issue with windy.com.

The former, being more open, could perhaps be interested in more
compatibility.

Riccardo