fucking pink unicorns

anyone know when that pref was added

therube frg are these bugs currently added to your mozilla base for 2.53?

446344 was already in 2.57, was added to 2.53.13b1pre

So this has been implemented starting with Firefox 59, but defaulting to disabled; Firefox 70 set it to 2 (always send) by default.

(bug 1424076)

njsg: indeed

446344 doesn't look that difficult to backport to the Aura Runtime Environment

was there any further followups made with it?

that are apperent?

njsg: do you know if the 59 to 56 port was pretty much as-is?

I would have to agree with that pref set to 0 m-esr91 loops forever

CapTainTobin needed a minor rebase for the 2.53.13 code but pretty much as is. the followups are harder to do.

hi! any chance somebody's using Vimperator or Pentadactyl (or may be some other similar Vim-like extension) with SeaMonkey? is it possible?

frg_Away: what about bugs 1504085 and 1566295

didn't have time yet. The files do not even exist in 60 and need to check if I can/want to add them as a prerequisite first so that the stuff applies clean. As long as you stay with value 1 probably safe.

yeah but will value 1 pass cloudflare's shit?

well that's gonna be even HARDER to test

because i just passed through the check

by doing nothing at all

yeah I can't get it to trigger a bad response in any UA mode now

so I will put this on the back burner until later i guess

or do the main bug and leave it disabled

or at one

why is 2 unsafe?

CaptainTobin yes for all sites so far. therube tested and I and njsg too.

might send headers when it should not and have privacy disclosure problems. But can't say I am a firm with this so need to check first. As long as it is same origin should not matter.

fanfiction.net did bring up a hcaptcha, & i'm not quite sure what happened with that exactly, but back-arrow then loaded the page. & actually, with that site, simply disabling JavaScript allows the page to load. (don't know if there are further issues there without JS?)

I am guessing 2 is refined with those followup patches based on a fuck-ton of refactoring in netwerk and dom/security

no captcha for me

therube: they HAVE changed something but Pale Meme users were reporting captcha PLUS infinate reload

yes, in PM that does happen.

so why not in Borealis

functionally save for GMP and EME and mac code.. UXP 5.1 and ARE 5.0 are functionally identical

who knows, maybe it's just a UA thing (on particular sites) ?

for the moment

frg_Away: I do have ONE regret.. That i sent 8 years working on Pale Meme and associated projects instead of SeaMonkey

maybe if I had done the work here instead of merely bitching at all of you to do it.. things would be better

and now that I have the skills and experience I have gained they aren't much use here beyond looking at bugs and finding shit because there are still things and ways of doing stuff that have to be dealt with in a specific way

and I can lobby for superior options all day but the shit I pulled during that time doesn't inspire a lot of trust now.. of which i can only try and make up for but still.. the world ain't as stable as it used to be

Well what is the saying A fault confessed is half redressed?

that's a new one for me

i guess fanfiction wasn't really a good site to reference, as even (now ?) in PM, it is allowing access (after 1st going to the cloudflare screen)

I personally just wish that more people would vcontribute. I can take the mozilla stuff all day if needed but can't say I like it. Things like rust are just good for the programming language dumpster.

That reminds me.. there are still some stubs for early rust hanging about.. I should clean those up

frg_Away: rust is literal corrosion on the codebase

perfectly named

eh?

code rust :)

we need to unite to fight the one and only enemy: Microsoft, er, Google

oh, and to get webdevs to stop chasing shiny

speaking of bloat

go here: greysheet.com/world-paper-money-prices

choose any random country

enjoy your browser eating all of your CPU

(no "unresponsive script" warning pops up - and the browser UI is still somehow responsive - only the entire site becames unusable due to some script gone amok)

lolCloudflare

tomman fine with NoScript and only greysheet enabled.

so a third-party script, eh?

tomman enable cloudflare and it takes some time but eventually loads. DidnÄt try the others.

yeah but NoScript has a lot of baggage when using it and what it does can't even be tested unless you disable it AND clear every known cache ever and still its effects can persist

network console shows hundreds of petitions for jquery.min.js and owl.carousel.min.js from CloudFlare

...why the site tries to load the same two scripts over and over and over!?

plus the majority of users install it thinking it is an instafix for their privacy woes but it requires some indepth knowhow to operate properly.. especially the xul-based version

tomman: my guess is that it is expecting the correct response with the correct headers

that is what this whole origin header csrf crap is about

the browser is(wisely) telling "use the copy in cache"

and seems to be one of the big things they were checking for in the change they made what.. last week?

also any one notice that Mozilla started signing their omnijar?

guess that is one way to do it

well omnijars.. given they still do dist subdir

wait, this site is using TWO DIFFERENT JQUERY VERSIONS on the same page?!

WHY

(3.4.1 and 3.6)

is that even legal?!

because web developers aren't anymore

One is locally hosted, the other is served via ClownFlare

they are snake oil salesmen who get kickbacks from Google and other cartel members

ClownFlare

I LIKE IT

speaking of clowns, it seems that this site tries to load the entire catalog on a single page

haven't they ever heard about pagination?

Not even InfiniScroll™

just... load each and every banknote known to this catalog on a single page, combined with whatever toxic jQuery hellstew their "webdevs" have cooked there

not only it kills client performance, it also eats bandwidth too!

these guys are good selling money... not so much buying competent IT

I would complain to them (there is a chat widget), but aside of the obvious expected "CLOSED WONTFIX USECHROME" non-solution, these are the same folks that bought a well-known banknote catalog just to kill PDF downloads for their subscribers

so screw'em

well if you have site specific user agent overrides and the page has more than 6000 images.. you might have a performance drop off too

best remove it like Mozilla did ;)

sorry but that one always gets me..

it seems it's their "Owl Carousel" script causing the weird delays

the scripts don't even wait until the page has finished loading

likely dependant on 800 different libs all compiled on the fly from a nodejs backend and then shoved into spidermoney asyncronously using dyanmic es modules that load and unload constantly

because that is how the "modern" web works

i may still be slightly bitter about some things lol

does it show?

still.. I can load a very long text or html file and (once it is fully loaded and the UI thread unhangs) scroll top to bottom with no issue.. wheras with Firefox and Chrome it may NEVER fully load and even if it does it will invalidate more than a few viewport size chunks above and below making reading large ass documents literally impossible

i assume 56 doesn't have this quantum change where the document in question is both there and not there at the same time

FWIW, the behavior is mostly the same on FF91ESR

(although the UI is far more responsible there, but the CPU impact is still huge)

CLOSED WONTFIX USECHROME BUYAMACM1

oh i know because the behavior is the same in chrome

the site IS STILL LOADING on FF91ESR, with my laptop fan at full jetblast!

do any user of this catalog ever manages to get results from it?!

ooooh, you also get those scary mixed content warnings because they're serving those banknote images over unencrypted HTTP

And that's the content you get for free, can't imagine how hard my computer would get abused if I paid those folks a $15/mo subscription to access the full catalogs...

"if you're collecting banknotes, you can afford a new Mac", I guess they would say

if you're collecting banknotes you can afford to have loading issues be someone ELSES problem

...not really, I could buy a bunch of rare bills for the cost of a new Mac

i mean you can pay someone else to find everything and make it their problem

apparently collectibles catalog sites AND JavaScript/Chromeisms™ serial abusers go hand in hand these days

tomman: we shouldn't have let HUMANS on the internet

that is the problem

what other of my hobbies have JS/Chrome killed/nerfed recently?

anime imageboards, numismatic catalogs...

soon

animorph chanboards tend to be coded by memestrs so some may not be AS infected

what about Pixiv then?

that place has come up before

Japan's very conservative 1990s Internet have finally got infected with the Chromeisms™ pandemic

that's plain sad

things like webp being sent as gif mime.. user agent sniffing.. js abominations

and i am sure webcomponents eventually

oooh, bugtrackers requiring Google WebComponents™

that's where you draw the line

tomman: yeah

well it sure prevents people filing or catching up on issues when webcomponents fails or is non-existant

you can't even READ tickets without WebComponents on, say, Monorail

a bugtracker is the LAST place in world where I would expect "disrupting technology"

...one of my banks is already threatening to deploy that garbage soon, too

...which is curious, because they still use IE and 16-bit software on their branches

(their ATMs still run XP, too)

Windows 3.1 used in airline software

well, they finally upgraded then :D

they were using IBM mainframes last time I bothered checking :)

numismatica.info.ve/en <= this catalog is a rare island of sanity in a sea of Google-induced insanity

browser-agnostic? YES

does not require JS? YES!

the guy knows that paging exists? ALL OF MY YES!

(Well, it uses jQuery, but sparingly)

of course the site is not for profit, so that means it doesn't need to appease to the Mac/Chrome generation

The Cloudflare protected sites all seem to work OK now with a default Firefox/68.0 SeaMonkey/2.53.12 UA. Prior to yesterday, using a UA of FF 100 worked on 80% of them.

tomman: greysheet.com/world-paper-money-prices - works fine for me with a default SM using a Firefox/68.0 SeaMonkey/2.53.12 UA

Rahul: have you picked a country/bank there? That's the page that goes insane, both on SM 2.53.12 and on actual FF91ESR

tomman: Yep, just tried 3 different countries and banks and they work fine. FWIW I use uBlock Origin, but we all do anyway.

need to figure out what exactly I need to block there

this page uses scripts served from Cloudflare and Fontawesome, aside of Google tracking (which I block via DNS anyway)

tomman: bugtrackers requiring something specific is really urgh

requiring javascript is bad enough. using gitlab or github.com for issue tracking is really narrowing down your audience too much

njsg: While I can understand the appeal of Gitlab/Github (selfhosting is hard AND costs money), what I don't get is why build something that should be as simple and robust as possible like a bugtracker must be done over the latest shiny Chromeisms

like, the case of Monorail

in the case of Github, you can at least read SOMETHING

in the case of Gitlab, it degrades further, but you can at least read the bug description

in the case of Monorail, you get a blank page

And people wonder why I go with Trac whenever I need something simple on premises (or can afford selfhosting)