15:37:20 hi frg_Away 15:37:39 Hi NewTobinParadigm 15:38:09 did you give any more thought to what would be useful to you on xr.binoc? 15:41:55 know what I like is that searchfox seems to explicitly exclude codebases Pale Moon has been on 15:42:04 24 38 and 52 15:43:29 but that's ok.. and even though I am not with /them/ anymore my cross-reference will continue to have a wide selection.. because well.. i can lol 15:43:33 Not much. Was deep into releasing the next beta with IanN and doing backports. I have "arranged" myself with the current stuff mozilla provides but as stated would like to have the latest 2.53 beta or relase branch from gitlab. I can live with dxr. I occasionally miss the older branches but annotate or local history with tortoise hg usually is ok. 15:44:14 i have the release branch but you are branching with different branches every time so is there some sort of feed so i can switch it out and reindex when needed 15:44:50 if you HAVE a branch i can just put in and have the script do it automatically like a beta or master or trunk branch then that can be automated 15:46:29 comm-sm2.53 is currently set to 2_53_11_1_final with the reletive mozilla srcdir included 15:47:30 NewToBInParadigm IanN is usually creating the branches. I usually populate them when we are all ok with the patch queue but a bit later. It is a bit of a mess and don't think can be automated. 2.53.12b1 is done and will be set when we release it as default 15:48:35 wonder if there is a way to query which branch is default from gitlab 15:52:55 git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@' seems to work but i dunno if that will stay valid if you change said default branch 15:53:42 I would however strongly suggest you go back to a trunk and release (tagged) or trunk and relbranch style at some point 15:55:15 I'll file it away until your next release and test if it does that and if it shows correctly i will add custom logic then I can.. SET IT and FORGET IT .. like a Ronco Showtime Rotisserie! 15:56:02 as for beta branches.. i dunno since there is nothing to query i don't think i can do much without staying on top of it.. unless you simply wanna provide a file somewhere with the branch names I can just curl down 15:56:05 I dislike this as much as everyone but using mercurial queues makes backporting really really easy. We can shuffle stuff around and fix it if errors are found later. Saves time and this is something we don't have enough. The l10n repo is basically traditional. 15:58:13 well if you prefer hg maybe look into some of these free options https://www.mercurial-scm.org/wiki/MercurialHosting 15:58:19 NOT SOURCEFORGE lol 15:59:03 If it helps I think putting the current branch name into a file in master is something easy done. 16:00:04 https://foss.heptapod.net/seamonkey is now basically the base. 16:00:26 Reminds my to sync l10n with gitlab :) 16:02:16 like a release-branch file with one-line on each would be very helpful 16:04:06 treat it like version.txt (no new line please) 16:05:49 http://personal.mattatobin.com/image/capture/592c6bc1-2317-489c-a411-d0c38399e0c5.jpg 16:07:34 IanN any preference for a file name in gitlab containing the latest branch version with current source? 16:09:16 what I need is a list of corrosion identifers so ident can search it 16:09:23 have to do that one day 16:11:50 "The Binary Outcast Cross-Reference Tool is a PHP executed hacked version of the Perl MXR tool which is a hacked version of 20 year old LXR." 16:12:53 yes.. I wrote in php a way to execute perl cgi 16:13:09 the reason is I am VERY SLOWLY moving functions to PHP 16:14:25 the only thing I won't be able to move without a bunch of work I don't have time for is identifier search and source file view (because of identifier linking).. dir list view, free text with glimpse or something more modern, and find file is basically trivial and i will get to it eventually 16:15:51 but i have a lot of OTHER infrastructure and projects to manage so.. that takes priority especially since everything I personally do I am doing basically alone now 16:16:11 BTW I am gonna revive and fork InstantBird for some reason 16:18:14 frg_Away: release.txt? source_repo.txt? 16:29:28 latest_branch.txt? 16:31:09 IanN latest_branch.txt sounds ok. 16:31:17 what about relbranch.txt and betabranch.txt? 16:32:03 cause you wanted beta as well right? 16:32:49 I can live with only beta /latest but yes can be split 16:33:22 which would be more useful? 16:33:26 beta or release? 16:34:18 or you just want what is effectively seamonkey-central just with this crazy branch setup right? 16:34:27 which is fine by me 16:35:01 and that means less logic to code up 16:35:29 I think having beta would over complicate things 16:36:08 well cross-refernce code search for current release is less useful for day to day dev than cross reference for current trunk or beta whatever your dev branch is 16:36:45 i will do both if you want that isn't a problem just need to know what would be useful to y'all 16:37:52 Usually few changes between beta and releae. I would just go with the latest branch be it beta or release. That is the most current in gitlab. so 2.53.12b1 2.53.12 2.53.13b1 2.53.13 and so on. A latest_branch.txt would be ok then. 16:39:39 what would you like it called? seamonkey-central sm253-latest? 16:41:32 central is still comm-central and would be confusing sm-253-latest 16:42:29 back in a minute 16:42:31 is seamonkey-latest253 ok? 16:42:39 kinda have a naming scheme going :P 16:43:00 seamonkey-latest2.53* 16:43:46 is seamonkey-latest2.53 ok? 16:43:49 kinda have a naming scheme going :P 16:43:56 didn't crash :) 16:44:29 I'll also add comm-central right now to the list 16:44:53 ugh comm-central doesn't have a proper git mirror does it 16:46:34 If you want to stay with the old names maybe comm-release-sm56-latest and mozilla-release-sm56-latest but overall pick a name and I am ok with it. Other than central don't think anything elase is confusing. 16:47:12 bit verbose 16:47:35 but no for your repo i was gonna have it index mozilla along with comm 16:47:45 tho comm-central and mozilla-central are seperate 16:48:43 http://xr.binaryoutcast.com/comm-sm2.53/source/mozilla/config/milestone.txt 16:48:47 see ;) 16:48:56 also that version is fake lol 16:49:28 cause it is a modified m-r56 in reality 16:49:40 Yes it is better 16:50:31 yeah since you changed the mozilla version you can't go back to what it really is .. that would cause issues with extensions adapted already and might even piss off aus 16:50:36 oh well 16:50:52 but there IS a more proper way to do it if you need to bump the rv version 16:51:04 in a later codebase 16:51:40 it has been a while since I used hg 16:51:47 is it hg pull or hg checkout? 16:51:49 Yes I wanted to set it to 56 back a few months ago but then web extensions did choke. We still build Firefox from it for tests and a-b testing. So 60 is it for now. Actually basically all of the 57 changesets which are not too nasty are in. 16:53:15 ok hg pull is effectively git fetch and hg checkout is effectively git pull 16:54:16 I thin hg and git clone are more or ess the same. 16:55:44 but statyed with 56.x for Thunderbird there. 16:56:15 Good fro a-b testing too 16:57:14 hg pull should be the command 16:57:20 ugh i simply can't remember 16:57:47 i think i am confusing my self remembering client.py 16:58:19 hg pull 16:58:19 16:58:19 Pull all new changesets into local 16:58:22 yeah 16:58:24 ok 16:58:38 Install Tortoise Hg. I use the command line but the gui is a lifesaver. Shows you the commands it executes too so you can pick them 16:58:57 heh well this is on a linux server so.. 16:59:21 i haven't ran tortoise hg in .. a decade? 17:00:38 Available for Linux 17:02:16 gui integration is only available for gnome and I am on kde but the gui itself is fine there. 17:02:37 I don't run a GUI on my servers 17:03:50 Yes for automation it is not the tool. Just if you want to work with repos. 17:13:11 oh man 17:13:17 Pixiv went full Chrome 17:13:32 Google WebComponents® are now mandatory beyond the login page! 17:13:41 ridiculous 17:13:58 Japan was the last standing man on the pointless Chromeization of the web 17:14:07 ...I guess that ended right now 17:14:57 to be fair Pixiv's UI was laggy as hell since they drank the SPA kool-aid, but they just went full-in with WebComponents® in the last few days 17:15:17 http://xr.binaryoutcast.com/comm-central/ 17:15:18 CLOSED WONTFIX USECHROME HEALTHYECOSYSTEM 17:15:20 frg_Away: 17:15:44 we will know in an hour if my updated script works 17:16:01 http://personal.mattatobin.com/image/capture/3b8affeb-44c4-4098-bd85-8d2e1c5c9035.jpg 17:16:03 should 17:16:31 i still need to make it so it doesn't do everything every 6 hours but the comm-central and hg part is done 17:18:01 still think i am gonna have to make a major modification to get it to conditionally re-index so i will save that until i get the sm latest going good 17:18:27 likely will ALWAYS run for c-c and m-c 17:18:36 cause way too commit happy 17:19:43 hmmm, enabling dom.webcomponents.enabled is enough to "fix" Pixiv, but of course that can break more stuff elsewhere 17:19:52 tomman try the latest 2.53.13b1 pre. has the patch from buc for optional chaining in. Together with Nullish coalesce op unbreaks lots of sites. Depending on what pixv uses setting dom.webcomponents.customelements.enabled and dom.webcomponents.enabled might work somewhat now too. At least gitlab and github are almost displaying ok with it. Setting them permanently to true not recommended. 17:19:58 wonder at which extent Pixiv is using WebComponents® 17:20:26 frg_Away: awesome~ 17:20:46 please excluse the inital commit message.. after what happened i was very angry and cross-reference was one of the few repos i didn't have a local clone of and lost but the code for it lives here.. https://code.binaryoutcast.com/infrastructure/xr 17:20:54 Maybe like gitlab initially for emoji support. Core stuff for sure... 17:20:58 patches welcome 17:21:56 frg_Away: just enabling dom.webcomponents.enabled lets Pixiv work (of course I'm aware that it's a global switch and enabling it all the times can lead to Bad Things™ happening) 17:22:03 In fact.. I am gonna force push a revision 17:22:17 I guess it's yet another case of "our 3rd-party framework just pulled that on our last point release" 17:23:11 fixed 17:23:39 will try .13b1 as soon as my DSL stops wetting the bed, has been working terribad since last Wednesday 17:24:05 frg_Away: I likely have more webcomponents than 56 does but yeah same deal.. it is literally an all or nothing evil spec 17:26:26 I am at about 59a1 with custom elements now. shadow dom is a bit behind. stylo would be working in theory if it wer not for the rust compiler crap. Old version does not work any longer and new version needs new bindings code. But unless 10 devs show up and we could remove this crap it is mandatory unfortunately. 17:27:04 what I would like is to have the power to force the entire Internet to stop using Google WebComponents® 17:27:19 I've yet to find a single developer to tell me what's so great about that crap, aside of "well, it's modern" 17:27:41 I'd say aura (and uxp) is somewhere between 62 and 65 with some parts older some parts newer.. we do NOT have dynamic es modules but do have basic es modules.. it can't progress further without ::slotted and another one i can't recall off hand 17:27:50 who killed server-side frameworks that we now must push page processing client-side?! 17:28:00 and because it was stylo there was no nsLayout version to work off of 17:28:28 tomman: well thanks to Moonchild loosing us the browser war .. it ain't likely 17:28:39 well that and Mozilla surrendering 17:28:51 I blame webdevs rather than browser devs 17:28:56 As usualy the theory of using components is fine. In practice only used to enrich google. 17:28:59 webdevs never asked for this 17:29:04 it's the same reason of why Mac sells 17:29:10 they didn't ask for hardly anything of the past decade 17:29:15 this is ALL google engineers 17:29:20 and sycophants 17:29:25 and Mozilla allowing it 17:29:41 and webdevs jumping into the fray because "oooh, shiny, must profit!" 17:29:46 real webdevs don't use this shit.. 17:29:53 why would they 17:30:06 too bad "real webdevs" are like dinosaurs, they're largely extinct these days 17:30:18 nowadays everybody relies on multi-megabyte JS frameworks 17:30:35 Eich said js was an abomination when he wrote it 17:32:07 and if he had not been purged for disliking the gays getting married maybe Mozilla wouldn't have surrendered so quickly and Eich wouldn't be a chrome shill using deceptive practices to temporarily steal money from people under false pretenses 17:32:42 his purging really broke him 17:32:43 in the meanwhile, even cellphone software is nothing but more Chrome-in-a-can 17:33:06 magic slabs of glass have done more damage to us as a species as anything else 17:33:23 In any case, I'm still waiting for the first webdev that can give me a honest appreciation of why Google WebComponents® is so great 17:33:51 what you can do with that horrible spec that you can't do with vanilla JS (or even better: server-side!) 17:34:24 heh, and people DARED complaining about J2EE/JSF by being bloaty horrible enterprisey crapola, but IMO it's saner than anything JS 17:34:33 WebComponents at its core is a twisted version of 20 year old Mozilla concepts that were sabotaged by mozilla them selves 10 years ago 17:34:36 prove me wrong 17:34:51 didn't even MS tried that two decades ago with HTA? 17:35:01 (and failed miserably) 17:36:24 HTA was never XUL and XBL 17:37:24 and Mozilla thanks to their arrogant 2010s bullshit sabotaged their own mature technology only for Google to reimagine it in the worst possible way years later 17:38:04 if Mozilla could have solved remote xul's security issues.. we'd be golden and it WOULD be the defacto standard for webapps 17:38:20 modern webapps 17:38:47 the only reason it didn't happen was because it wasn't allowed to 17:39:32 xulrunner, remote xul, et all would be king over anything Microsoft would have come up with and Google would have had to support Mozilla technology 17:39:46 not electron and webcomponents 17:39:59 or xaml/directui 17:40:01 I do not want webapps everywhere, that's for sure 17:40:18 I get it, native development is hard (and another can of worms), but it exist for very good reasons 17:40:40 stop trying to turn the browser into a full-blown OS! 17:41:28 even cellphones have to endure endless layers of bloat because every app is another Chrome-in-a-can™ of unusable bloat 17:41:43 well with javascript being TURNED into something more complex and ridiculously opaque as any native binary especially with webpackage (webpack?) yeah 17:41:44 (not everyone can afford an iPhone X or Galaxy S) 17:41:58 boot2gecko was never gonna be successful 17:42:02 and kaios still isn't 17:42:18 xul fennec was screwed over 17:42:19 I own a KaiOS phone because I'm masochist, I guess :P 17:42:26 i have one as well 17:42:26 it's as terrible as you can imagine 17:42:34 and with 256MB RAM, well, ouch 17:42:36 it is more terrible than I imagined 17:42:48 it is like whoever works for KaiOS has never used a cellphone in their lifetime 17:42:50 my 2004 feature phone runs better 17:43:09 there is LITERALLY a 1.5 second delay between keypress and action 17:43:14 how in the hell you come up with a phone UI where rooting is required to change the SMS ringotne?! 17:43:15 it is pathetic 17:43:52 reminds me of old Verizon cellphones where everything was locked down behind crippled firmware 17:43:59 but at least those were fixable 17:44:16 anyway.. if you wanna see what a communicator PLATFORM codebase looks like keep an eye on the Aura Runtime Environment heh 17:44:31 I am spreading netscape design throughout the toolkit! 17:45:22 xpfe design will return! 17:45:38 next to me there are three cellphones on top of an old Pentium 4 laptop: a KaiOS turd, some cheapo Snapdragon-based Android 7 Alcatel 17:45:43 and a fresh out of the box Redmi Note 11 17:45:47 i miss xpinstall 17:45:52 ...all of them are terrible compared to the P4 laptop! 17:45:59 i'd KILL for someone to reimpl full xpinstall 17:46:11 why did Mozilla kill that technology 17:46:35 a cross platform installer tool common to install, update, add-ons, components 17:46:41 it was absolutely stellar 17:46:50 forgot the "monetization" part 17:47:01 i am just eBegging 17:47:07 that IS my monetization 17:47:34 you need VC funding, the IPO, unicorns, and just to be safe, crypto/NFTs 17:47:37 https://code.binaryoutcast.com/projects/aura-central/issues/14 17:47:41 ;) 17:48:33 also, getting Musk tweet about your stuff always help 17:48:51 good luck making THAT happen 17:49:29 if Musk tweeted he used SeaMonkey.. you could TAKE OVER comm-central and fund a whole infrastructure and buy out the trademark from mozilla 17:49:38 it's the same guy that shot Dogecoin near the $1 point (and back), and that considers Touhou wolfgirls to be catgirls instead 17:50:11 so weirdest things have happened :D 17:50:15 I'm a Dalek. 17:50:27 but you knew that already 17:50:35 gitlab now has a latest_branch.txt in master: 17:50:37 https://gitlab.com/seamonkey-project/seamonkey-2.53-mozilla/-/commit/5751ad0af32c6ff596fe66546fd2d537116ac07d 17:50:39 https://gitlab.com/seamonkey-project/seamonkey-2.53-comm/-/commit/2afd66851dbab3114e9859690f87bf5442cedabc 17:51:38 Need to do some real life stuff now 17:52:28 frg_Away: I'll get this done today just not this second 19:49:31 2.53.11 isn't displaying the whole page, missing most of right column, and missing comments following the first: https://gitlab.freedesktop.org/drm/intel/-/issues/5711 19:50:03 what does the Toolkit Error Console or DevTools Browser Console say a-865 19:51:13 Timestamp: 15/04/2022, 15.50.55 GMT-4 19:51:15 Error: TypeError: e is undefined 19:51:16 Source File: https://acsbap.com/api/app/assets/js/acsb.js 19:51:18 Line: 1 19:51:39 is that the only error? also perhaps pastebin em? 19:51:49 this is constantly repeating 19:52:35 only error I get is invalid regex group but my codebase is older than sm-latest 19:52:47 i don't have seamonkey available atm 19:53:01 there are others, but the window scrolls so fast they disappear before I can copy... 19:55:16 closing the tab leaves the other gitlab tabs doing the same 19:58:16 try the browser console 19:58:28 won't be as nice imo but shouldn't flow away 19:58:32 as fast 20:01:13 I tried copying one field to a text file to paste. Paste fails, 237k bytes O_O 20:08:47 constant stream of errors from all over the place 20:08:51 doesn't GitLab requires JustOff's addon? 20:10:36 https://github.com/JustOff/github-wc-polyfill/issues/45#issuecomment-1087765302 20:10:42 https://github.com/JustOff/github-wc-polyfill/issues/45#issuecomment-1098584151 20:11:07 you need an OLDER version of the addon because lolGiggitylab and lolFreeDesktop 20:12:12 ...except that nope, 1.2.16 won't help 20:13:12 ...but updating to 1.2.18.2 works 20:13:18 (I had to open a fresh tab) 20:13:43 now I can read the whole ticket 20:13:50 SyntaxError: invalid regexp group commons-pages.admin.topics.edit-pages.admin.topics.new-pages.groups.milestones.edit-pages.groups.mil-2c3731d7.9d206744.chunk.js:1:285 20:14:05 got that from browser console after reopening closed gitlab tab 20:14:14 a-865: you need JustOff's github addon to work around that 20:14:24 make sure to install the latest 1.2.18.2 release 20:14:42 https://github.com/JustOff/github-wc-polyfill/releases/tag/1.2.18 20:15:30 bugtrackers ARE supposed to be solid, simple, reliable software with as minimal dependencies as possible, so why do they need emoji regexps!? 20:15:31 WHY 20:15:54 > Does this page need fixes or improvements? Open an issue or contribute a merge request to help make GitLab more lovable. At GitLab, everyone can contribute! 20:15:57 the addon works 20:16:11 where "everyone" means "everyone using Chrome, of course" 20:16:57 tomman: anything to bloat their pages more :p 20:17:00 also, seriously, emojis ON the developer console!? 20:17:16 soon, we'll have emoji-driven development 20:24:00 i still intensely hate JustOff 20:24:02 btw 20:24:05 that will never change 20:24:19 attempting to open the invitation to new issue opens this instead: https://unagi.amazon.com/1/events/com.amazon.csm.csa.prod 20:24:31 that is why I turned his bootstrap extension into a jsm and am building it into my navigator 20:24:37 it just needs updated 20:26:29 seamonkey-latest2.53/source: Changing branch to 2_53_12_beta_01... 20:26:35 well amazingly that works 20:27:24 http://personal.mattatobin.com/image/capture/a8f03651-6dba-4c03-ad71-6f7870fee4f0.jpg 20:50:40 https://gitlab.com/gitlab-org/gitlab/-/issues/359320 20:52:40 ok the final path is http://xr.binaryoutcast.com/seamonkey-2.53/ it is just simplest for my setup 20:53:04 it is indexing right now 20:56:06 unlike orginal mxr i exclude MOST tests and sqlite3.c so it doesn't take 45-90 minutes to run the identifer search 20:56:12 just be aware ok frg_Away IanN 20:56:39 ok 20:56:54 IanN: must be familar seeing that working again 20:56:57 heh 20:57:09 especially for you my good and dear friend 20:57:24 thanks bookmarked 20:58:09 i have it set to pull at 0 6 12 and 18 UTC .. should be sufficient 20:58:30 and especially now that i HOPE i have it ONLY running the regeneration if needed 20:58:38 thanks for the push to actually do this 20:58:41 it deff helps 20:59:19 oh.. ident doesn't have rust support yet.. if that matters to anyone 20:59:33 i could add it but i'd have to know the language constructs to do it 21:00:03 I personally have little motivation as rust code doesn't help my process at all 21:01:07 oh frg_Away have you had any luck getting nss past 3.64? 21:01:18 a-865 they don't care. The last issue Waterfox opened was a gem. First some back and fouth between units and then basically a fork off. From a market share perspective I could understand it. But trying to give yourself the good buddy image and then doing what any shitty corp does... Well if you have no expectations I can't complain. 21:02:00 cause in my tree while I got it working with gyp.. it started well spewing odd and illogical errors within dom indexeddb and gfx components for no rasin 21:03:38 NewTobinParadigm It should work fine but I didn't have the time yet. Still on the esr78 version but now already three backports. Linux distros compile against it and as far as I know it works there. Not that I like it. 21:04:19 ah right.. system nss 21:04:29 Yes 21:04:31 i don't allow that .. another complication i don't need 21:04:59 well in-tree on my codebase i got it up to 3.64 fully functional 21:05:03 but no higher 21:05:54 nss and nspr now apply clean to our tree but I always check the bugs for needed other changes. Neither me nor IanN found the time yet. 21:05:55 frg_Away: did you try teaching nss to not build with avx2? 21:06:11 i dunno if it is required for your level but it was for mine 21:06:23 https://code.binaryoutcast.com/projects/aura-central/commit/a6b6fc29a6a7ef012feb5e698a5cba71c60b5ed3 21:08:12 Didn't change anything here with the ESR78 versions. Still rune fine on Core 2 Duo. Offcial builds use VS2019 for x64 and clang 9 for x86 under Windows. clang 9 macOS and gcc 8.3.1 Linux 21:08:27 that was the gyp followup to https://code.binaryoutcast.com/projects/aura-central/commit/2c885c3249161c8eb836abda35df351609fc5102 21:08:39 oh 21:08:42 tomman: I blame google and w3c :-P 21:08:44 that was because msys 1 21:08:48 ok 21:08:57 you use mozillabuild 3+? 21:08:59 for you 21:09:17 mozilla build 3.4 latest and greatest 21:09:28 yeah the codebase requires modifications to use it 21:09:30 i believe 21:09:38 i haven't researched it yet 21:09:51 just been spot updating mozillabuild 2.2 with updated components 21:09:59 nsis 7zip and the like 21:10:10 but keeping msys reletively untouched 21:10:35 just got tired of using some versions of stuff from 2016 and older 21:10:41 especially nsis and 7zip 21:10:50 ah ident is complete 21:11:03 I have not build a 2.49.x in some time. Needs VS2017 and mizillabuild 3.3 or 3.2. Some of the defines are not expanded correctly in the build files. I needed to fix it for 2.53 21:11:28 <+tomman> it is like whoever works for KaiOS has never used a cellphone in their lifetime <-- so, like many android smartphones? 21:11:41 yeah but your vs2017 hack was still using the vs2015 compiler i believe 21:12:02 Bug 1692200 21:12:16 in order to move forward with my plan which i no longer have the skill pool for to update spidermonkey wholesale.. i need to first get the codebase building with 2019 21:12:23 So 2.49.x is confied to 3.2 21:13:20 if shit hadn't hit the fan by now we'd be pursing our plan to start wholesale updating spidermonkey up the ESR train 21:13:38 i have little doubt i could get it to ESR60 by my self. 21:13:47 2.53 is up to VS2022 now. Needed some changes for the directory structure. Mozilla dropped support for it but I like to have a second compiler around. 21:13:59 i have the build system and research skills to manage it.. but past that i am sure it would get harder 21:14:23 there is no point to going past 2019.. one because visual studio is fully a service 21:14:30 and two.. Mozilla went clang 21:14:37 so why bother 21:15:30 by the time older visual studio is hopelessly obsolete and unobtainable.. windows as a platform won't BE enough of windows to matter anyway 21:15:40 I am now well into 58a1 patches but it becomes harder. Need to drop legacy generators which are basically broken already and the object getters and setters are really in the way too. nsIParserService and xmlrequest also. 21:16:09 i don't see a reason to drop stuff just because it is the progression 21:16:11 VS2022 is like VS2019. I only use the compiler from Community 21:16:43 outside js and dom and layout things could stay reletively the same for nearly ever and no one would care 21:17:41 i mean am I wrong? 21:18:35 gfx is a problem 21:18:45 in what way? 21:18:55 what old ass cairo? 21:18:59 angle? 21:19:10 cairo was royally screwed up 21:19:13 upstream 21:19:28 and mozilla never fixed it because webrender bypasses the issues 21:19:39 new formats and angle harfbuzz and the other stuff. 21:20:05 widget too. macOS and wayland needs updates. 21:20:20 heh.. i don't even HAVE wayland 21:20:44 i dunno if i will get it.. or if it is even worth it.. as wayland emulates x11 anyway and will never be allowed not to 21:21:13 We neither but it is just a matter of time till the 20 year old alpha phase will make way for a 100 year pre beta phase and x11 be gone. 21:22:19 I don't care about http/3 and quic and all the other junk but this might be needed too later. 21:28:26 frg_Away: did you ever add reader to seamonkey? 21:28:38 reader mode 21:28:52 No 21:30:36 Thanks to the everchanging web I am now doing 90% backports. Glad that IanN still finds some time to add new stuff to suite. I only now and then when I am fed up with ports. 21:31:13 frg_Away: you need to sort out cloning! 21:31:39 IanN well you failed me here. You promised! 21:32:09 frg_Away: task 9999999 21:32:45 frg_Away: or maybe task ∞ 21:33:01 nsIClone 21:33:22 that sounds like a Netscape function... 21:33:46 a scriptable interface to some ye 21:34:02 IanN task numbers starting with 99999 are reserved for me personally so better make it 99998. 21:34:09 IanN: did you forget xpidl? 21:34:32 xpidl sounds like ex-piddle! 21:34:55 ex pea eye dee el 21:35:56 cross platform interface description language 21:35:57 right, off to eat, bbl 21:36:02 enjoy IanN