/join ##palemoon

wsj.com is now giving me seemingly UA-based captchas, it will go away and let me through if I set a Firefox 118 UA. Now is this the same jwz blogged about some days ago? back then I couldn't reproduce. Maybe it depends on how new an article is?

yes it was jwz.org/blog/2024/02/my-device-i-am-told-might-be-unverified

(now I didn't get the spinner because that apparently runs on ECMAscript, or is loaded by a script)

in the meanwhile one of my banks deployed Clownflare on their homebanking portal

and it has been pure misery since then

not only Clownflare gets in the way every time I need to get bills paid

it also interferes when logging in into the bank - the first attempt after getting the captcha junk FAILS because of the bank page getting confused over a prompt to re-try a POST request

have to close the tab and try again - this time Clownflare is pleased and lets me login... but a few hours later the cycle repeats

if I didn't had my one and only international debit/credit card with this specific bank, I would have already closed my account out of spite

(name and shame: online.bancamiga.com/?p=1 )

thanks tomman

why cant we just have simple html

even a symbian phone can render it properly

amazingly no bank yet is enforcing "latest Chrome or Chrome or Chromefox ONLY" system requirements in Venezuela (mainly because many still use XP or 7 at their branches)

but there have been attempts to sneak in the Chromeisms, like banks switching to toxic JS frame-not-work hellstew

now, the homepages are another thing - two of my banks here have pages that won't render on anything but a "evergreen" browser AKA Chrome

but I don't bother with homepages - they're 99% of the time useless, especially when you're looking for requirements for $PROCEDURE, then you walk into the branch and found out that the webpages were full of lies

My homepage is about:

tho there is no about: page in modern mozilla

no root about page i mean

MattATobin: I seem to remember setting my home page to about:blank

well that works

but ye seamonkey's about page the generic about page for all.. gone

guess should add that to the list of c-c bugs lol

dont now if about:about woud work for what you want

about:about is a shadow of its former self lol

if thunderbird is anything to go by it seems they are just gonna use about uris rather than chrome uris for .. i dunno sheets of ui lol what do you call layers of nested browser elements as the ui?

other than the obvious lol

I wonder if removing "about:" was due to lack of fox usage or if the redirector module was retooled to not have a root page in the protocol

WG9s: as annyoying and frustrating and chaos inducing as it has been.. i love doing mozdev tho half of it is beause mozdev inhearently includes complaining about mozdev.. Perfect for me.

;-)

today i am gonna refresh my 2.53whateverpre build and start standard thrashing looking for brokenness as well as work on getting GOOD at basic fluent migrations

speaking of.. frg_Away what is sm's l10n situation how many langpacks are there?

MattaATobin 23 languages so 23 langauge packs and full installers including en-US

l10n is the most sanest of the 2.53 repos. hg and gitlab in sync at 2.53.18.1. Only one patch for upcoming 2.53.19 in the queue but can be left out.

why produce all the installers at that rate you should just have en-US and one .. ALL languages langpack and a dropdown somewhere

or ust build em all in

why not

MattATobin installers are better. There are still some wonky defaults wrt calendar and others in language packs. Multilocale stuff has not been backported yet.

stick with me here.. localized installers .. are not that important in this case cause almost no one will actually read it and just keep clicking next cause they wanna install it and its literal instinct at this point

but quirk avoidance trumps the hell out of that

so i agree :)

a lot of storage tho on your rel servers

is calendar in extensions or distribution/extensions

MattATobin so far it is not a burden so they can stay.

when produced

extensions. We dropped distributions for the bundled ones some releases back

ah good

so yeah installers would work best cause of the complexity of bundled extensions

IanN_Away fixed it for language packs but it was a treat. Noever worked right in orginal mozilla sources since 2.45 I think.

dropping xpinstall was a mistake

nullsoft has a nice installer but it betrayed the netscape tech