Sompi: I guess yle tends to be the exception for text articles with noscript, and yes, I think we've discussed some breakage already at yle too...

still, they did have full-text in feeds some years ago, which was even better. now feeds just have the "summaries".

And I haven't tried Areena in ages...

yes, even Yle is becoming more and more closed, and it is funded by our tax money...

Their RSS feed has became 100% useless

not 100% for me, it now means I can't read directly, but can still be used to follow their news

now I'd rather have the articles directly in the feed, yes...

but at least yle still has teletext :)

but yeah, rss feed becoming useless and not containing anything "above the fold" has become more common

and it's rare to just get article feeds

animenewsnetwork.com/interest/2024-…orts-starring-sumire-uesaka/.218446 omg NOOOOOOOO~!

tomman: well chrome is kawaii don't you know.. baka

what's next, Chromium The Isekai? :D

"My Web Browser Died And Reincarnated Into A Chrome Clone"

my guess it will end up down the line as a magical girl anime... but techwise

tomman: well maybe we need a fan-based parody of chrome

Chromium Abridged

or maybe we can get it to show up in the DevilArtemis universe for Cell to kick Chrome's ass

tomman:

assuming DA Cell ever actually fought anyone in those videos..

Another page that refuses to work with seamonkey: sciencedirect.com/topics/medicine-and-dentistry/fluorocarbon

It says "your browser is out of date" but I have the newest Seamonkey

It has a browser check and it refuses to show the content if the browser is not "supported"

why are "science" websites suddenly all doing this?

and why are they even doing that at all? on that page there seems to be nothing that would be impossible for seamonkey

Tobin: Chromium, an anime character which rallied to make hair extensions only 1cm long, and uses these to promote them, even if they're not that useful for the original purpose anymore

Sompi: seems to load for me although it may need CSS hacks to expand the content further (unless the extension is dynamically loaded...), so it's a needless check made with JS

Sompi: I'm not able to test that right now, but, if you didn't try that, check if a recent Fx UA makes it go away

of course it could also be that sect that does error "handling" in the fashion of "at the slighlest non-conformity with what we want, show 'unsupported browser' or 'browser out of date'"

I think the latter is nowadays more common

JavaScript has so many new "features" (chromeisms) that do exactly the same thing as some older, simpler and easier "deprecated" API does

And deprecating features from a locally interpreted language like JavaScript is just asking for problems...

There will always be web pages that use the old way of doing things

And why those new ways of doing things are always so ridiculously complex? It's like they aren't even meant to be used without some complex megaframeworks and libraries in between the programmer and the actual JavaScript API...

njsg: "in the fashion of "at the slighlest non-conformity with what we want, show 'unsupported browser' or 'browser out of date'"

"

<- they are probably relying on some undefined behavior in the "supported" browsers

it is increasingly common

<njsg> Tobin: Chromium, an anime character which rallied to make hair extensions only 1cm long, and uses these to promote them, even if they're not that useful for the original purpose anymore

i think i should add that to some fortune file :D

btw, what happened to quotes.burntelectrons.org

?

github.com & Assets. github.com/martok/palefill didn't seem to help.

PaleMoon uses a UA override for github, & while PM works (with override & whatever other code it may natively have), an override was not enough for SeaMonkey.

Palefill had stopped working long LONG ago on non-PM browsers due to some specific API that SM didn't implemented, IIRC

dom.getRootNode.enabled

IIRC frg even declined to implement that patch back then for sound reasons

the Unified XUL Platform has nearly complete support for shadowdom and customelements.

We need to implement more of shadow dom web components. I still hope we can make stylo working and then it would be a breeze but there are not enough hours in the day and people actually doing frequnt backports you can count using te fingers on one hand....

build system, frg.. it all comes back to build system..

I don't think so. You need to invest some time and thsat what 99.9% are not willing to do.

frg_Away: I do have one thing.. I am VERY close to ACTUALLY understanding the relationship between a xul custom element and its xbl forebarer..

to the point where I ALMOST understand basic custom elements

and i am getting a clearer picture of how the progression went.. its very facinating also intensely infuriating

time to update the nightly here~

any gotchas for today before I do The Usual™?

tomman should be very stable

going for it then, noticed it's now at .21

i need older deps to build the "nomans land" of late 60s to 90s specifically older cbindgen

tomman: did you survive?

apparently yes~

oh, the weird bug with cZ's user list seems to be gone

at least we're better than Pat Gelsinger :P

gcc pass 2

tomman yes since 11/06 I think

When we get stylo to work it probably needs xbl fixes and if not it probably needs other stuff and xbl fixes :)

frg_Away: at some point lingering XBL code not removed in the purge is slaved to shadowdom in refactors

the key is if XBL its self becomes a burdon to focus on perserving XUL features within xul customelements

becomes the next option

Not a fan of xbl but want to keep it for add-on comaptibility. But I find web components worse. Opaque and murky seems to be it here.

When was the last time that JavaScript got some new API feature that actually does something that wasn't possible before by using some older standard function?

EME

MSE

technically all the webcomponents wasn't possible before because xbl was never a standard anyone used on the web

but it certainly isn't NEW

the question you should ask Sompi when was the last time anyone did anything original in tech

I meant that many new JavaScript APIs seem to do things that were already possible by using some older JavaScript API

Well optional chaning and dynamic imports are ok among others. Turing js into a java bastard with private fields and others stuff not so.

And then they "deprecate" the old API, which is a very stupid thing to do in a locally interpreted language like JavaScript

its more about adding stuff to javascript and dom that have no business being in a document object model or event scripting language

the browser is an OS client

its why I keep saying navigator in contrast whenever possible

What functionalities do dynamic imports make possible that weren't possible before?

frg_Away: php is becoming js like on top of its pythonic nonsense additions

importing modules on the fly

its an eq of dynamically loading a jsm

that's why its there

The biggest problem is no real versioning and release management. just lets add stuff and call it the release the yera draft xcviii

this is all still in some shape mozilla concepts

But isn't that already possible?

remember

EMCAScript the only language with a Stage 4

^of the year draft ...

only other thing I can think of with a Stage 4 is.. cancer

well i never understood how javascript versioning worked past when EMCA not Mozilla was defining it

there was Javascript 1.7 and...

How HTML5 versioning works?

ES4x ES5 ES6 and ESLGBTQ+ i guess

Isn't it officially just a "running standard"?

"Living Standard"

So HTML5 can basically mean almost anything

but no semblance of a Standard of Living

;)

Sompi: yes

this is why all us lunar freaks were pissed a decade ago

well it was why I was pissed i dunno why they were REALLY i know I imposed me being pissed about it upon them.. that much is certain

I still prefer HTML 4.01 over HTML5 just because HTML 4 at least doesn't change all the time

If something _has_ to work _reliably_

no fuck you, xhtml/1.0 transitional

:P

It is also good

It's XML or nothin!

html 4.01 is better supported by old browsers

xml is our rightful future

I always write it in such way that it is also mostly html 3.2 compatible

I used to compat to gecko 1.9.x

maybe one day

I am tired of ignoring this lesser new technology

something I thought would be nice Sompi is if I wrote a JS lib that would just.. be "XBL5" as in read an nearly-xbl xml file and do the boilerplate for me.. like exactly how it was done before