01:42:32 <andr01d> It seems that just recently more github pages wouldn't display in SeaMonkey 2.53.14, even with github and githubassests allowing javascript. What is the lacked feature that prevents github from rendering?
01:42:57 <andr01d> I have been browsing github with all js and cookies disabled. Not all pages worked, but most of it did.
01:44:00 <andr01d> An example URL: https://github.com/home-assistant/operating-system
02:12:14 <ewong> github is a pain..  would work sometimes...  other times(most often than not)  fails to load things.  ;/
02:19:08 <tomman> GiggityHub keeps changing stuff every single month, sometimes even several times a month
02:19:26 <tomman> gotta use those latest shiny features (brought by Google, naturally!) ASAP :/
07:02:35 <njsg> andr01d: until months ago, you could browse and read files, until recently you could read the top-level README and see the top-level directory, and see commits. Now you can't even do that. for some reason, github can't deliver static content over HTTP, I wonder how did the web survive when javascript didn't exist
07:11:22 <Zart> github on SM has been unusable for a long time already 8\
07:11:42 <Zart> polyfills helped, but with forced 2FA it's now impossible to even browse it
07:18:18 <njsg> well, there are at least two different ways of interaction: scripting and no scripting
07:18:59 <njsg> it's rare for me to browse github with javascript enabled, so my experience is mostly focused in how it reacts to no scripting available
09:21:04 <hardys> WG9s: fyi, your server is down
12:29:41 <WG9s> must have been some internet routing issue my server has been up all along and works find from here.  also verizon did not rewubnet me such that my DNS is incorrect.
14:16:44 <frg_Away> WG9s works for me
16:10:56 <Px_x64> Hi, is creating/editing bugs in Mozilla Bugzilla on 2.53.18 broken for everyone? Last time I was doing this more than a month ago, and it was ok. Currently I'm getting garbled UI in Categories/Tracking sections with all text instead of selection menus. In console I see an error for
16:11:08 <Px_x64> SyntaxError: bad method definition
16:11:10 <Px_x64> select.js:15:9
16:13:04 <Px_x64> https://bugzilla.mozilla.org/static/v20240110.1/js/components/select.js - the file itself. According to the date in URL, updated 2 days ago.
16:18:36 <tomman> that looks like Custom Components, but the "bad method definition" is this:
16:18:38 <tomman> static formAssociated = true;
16:18:47 <tomman> a static member declaration on a class
16:19:19 <tomman> however that one is weird
16:19:21 <tomman> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/static
16:19:56 <tomman> class foo {static moo = true; }
16:20:05 <tomman> also gives a "bad method definition" error
16:20:14 <tomman> looks like that qualifier is unsupported here?
16:20:33 <tomman> yet MDN says that such feature dates back all the way to... FF45
16:22:15 <tomman> yep, static properties are not supported, static methods do work
16:22:50 <tomman> static initializers (class poo {static {console.log("poo!");} }) also do not work
20:34:04 <frg_Away> on the plus side much slower and cumbersome on a supported browser too so good job again.
22:41:37 <njsg> sigh, they replaced the select with a "custom element" so that it'd have "easier data input"
22:42:18 <njsg> so, no fallback? and also, I wonder if this shouldn't be something for the browser to implement