It is likely that the 12-years old and mentioned in all release notes bug 521861 is near to be fixed now. Any comments are appreciated. Let's fix it finally! :)

Apropos: seamonkey-project.org/dev should the reporting bugs link be working?

DMN changed their links

s/DMN/MDN/

DaMN.

Lightkey: ain't that the true ;/

I guess it's high time the actual build docs are placed internally on our site..

Lightkey: there must be more broken links in the site and in the help now. they removed a lot of "outdated" content

buc: for news://server/group URLs with 1.0.4, the account wizard pops up right after accepting the "do you want to subscribe to ..." dialog

on bug 784785 and bug 1720968: the drag and drop event is possibly generated in EventStateManager.cpp - for bug 784785 it looks like there is a minimum distance below which the drag event is - at least sometimes? - *not* generated, that could be IsEventOutsideDragThreshold()

buc: 2.49.5 with gtk2? patched somehow?

Hi there... in my profile directory there is a dir called cache2 -- can this (or the contentst ) of this safely be deleted?

njsg: "with 1.0.4, the account wizard pops up right after accepting" -- you mean SM version 1.0.4?

njsg: Nothing special with 2.49.5 with gtk2, since afaik even official versions <= 2.49.4 was built eith gtk2...

buc: yes, 1.0.4

buc: er, "yes, seamonkey 1.0.4"

buc: it's just that I thought 2.49.5 couldn't be compiled against gtk3 out of the box^Wtarball

er, gtk2

Oh, SM-1.0.4 . I still use the home button for modern theme from SM-1.x line...

Cool, let's create a Matrix account...

> The easiest thing to do if you want to just have a play, is to use the Element web client. You can use it as a guest, or register for an account.

awesome, a webapp, let's go there?

> Your browser can't run Element

well, Seamonkey is not welcome to the party

any other options just to create an account before my blood rage level goes off the charts?

(For now I intend to use it on Pidgin; maybe someday there will be an Android client not built on bloaty Electron... and of course the whole thing already failed the Granny Test™)

anyway, another webapp bitten by the Chrome bug :/

> Element uses many advanced browser features, some of which are not available or experimental in your current browser.

> Please install Chrome, Firefox, or Safari for the best experience.

that's... lulzy

Safari!?

ah yeah, Apple cellphone users are worth more than anyone using Not Chrome™

they told me there is hydrogen.element.io, but won't load on SM either

however, someone is going to check on it, which is nice

(that's their web client aimed at older browsers, it seems)

tomman I think the last time I needed to enable modules support but they might have "advanced" more so not sure. I don't care about matrix so never checked recently. Just another proprietary protocol with an open source whitewash this time.

frg_Away: all IM apps are terribad these days, but you're pretty much forced to use one

of course I'm NOT using WhatsApp

just registered on Telegram (I know it sucks, it's unsafe, etc, etc, etc), but normies are likely to use it, AND there is a Pidgin plugin for that, AND the cellphone version is not Electron junk and it's on F-Droid

if only Signal didn't went the assh*le way with its "ban" on 3rd-party clients....

why have a version for older browsers and use such a feature...

I mean, of course it's their choice, but wouldn't it make sense to try to steer clear of such features?

oh, Hydrogen breaks due to JS optional chaining operator

> if (body?.nativeBlob) {

(thanks for non-minified JS!

at least that'll probably be readable without javascript :-D

another dev says that on a clean SM profile it doesn't happen, although it still dies due to an IndexedDB error

(I'm on #matrix trying to get help right now)

the comments in that issue sound like they're serving different code to different browsers, so could it be the UA string? or perhaps something like modules being enabled?

or are modules always required for all browsers?

Does Seamonkey support IndexedDB (whatever is that)?

njsg ?. is not supported. Modules need to be enabled. I am on the last patches but wanted to put more "groundwork" in first. 3 or 4 missing but seesm to be non- essential

apparently my browser is picking out ES6 stuff when it should not be

my UA is stock, except for Google and Pontoon where I had to pretend SM doesn't exist

tomman indexedDB is old. Might be just another new storage api here. Put a lot if it in recent builds.

^a lot of it.

Hmmm, why dom.moduleScripts.enabled is ON on mine?!

my guess is that it was enabled before for some other site :-D

anyway, restored that and their sign-in form loads

...but I'm just told I can't use that to register a new account :/

wonder when I did enabled it, or for which site

well modules is not modules. Still in flux as is everything js.

"living standard"?

they've just filled that

njsg looks more like a petri dish standard :)

nah, I would call it the "hyperinflationary currency standard" aka the "Zimbabwean Dollar standard"

or was it the Venezuelan Bolivar standard?

anyway, when you have new banknotes obsoleting the older ones released last month every month...

Javascript and the web are kinda like that