13:38:30 uh-oh, the Github polyfills broke again :/ 13:38:49 TypeError: this.attachShadow is not a function 13:39:19 time to check JustOff's repo to see if he is aware of the latest load of Chromeisms™ 13:41:10 (accidentally forked a repo, now I can't delete because "Sorry, something went wrong" when trying to access the user menu) 13:42:15 https://github.com/JustOff/github-wc-polyfill/issues/43 oh, there is it 13:42:26 > GitHub is broken because of using ECMAScript2020/2021 features 13:42:33 OOOOOH SHINY!!! MUST USE!!! 13:49:27 nope, the updated addon doesn't help 13:49:31 https://github.com/JustOff/github-wc-polyfill/issues/19 looks like it's this 13:49:34 I find this use "Brave-based browsers or die" attitude very discriminating... 13:50:13 tomman: even latest 1.2.11 polyfill doesn't work? 13:50:24 JamminUnit: just updated to it, doesn't work for me 13:50:49 Oh, right. I cannot even open my user-menu anymore... 13:54:02 yay Chrome 16:09:52 https://github.com/JustOff/github-wc-polyfill/releases/tag/1.2.12 16:09:55 that was fast! 16:11:12 ...or not, the user menu no longer shows "Something happened", instead it shows... nothing 16:12:42 at least the repository menus now work (and irritatingly enough, there is no option to delete repo there) 16:32:40 Hey all, just started using SeaMonkey and I am really enjoying it. I am having some troubles though, that I can't seem to find the answers to regarding mail. Every time I attempt to send an E-Mail, nothing happens. The same when I attempt to reply to an E-Mail, there is no quote and no 'to' address either. Has anybody else run into this? 16:33:59 which version? what did you configure in Mail&News so far? (accounts, smtp servers?) 16:34:30 if everything is configured, it's probably worth checking if there's any new error message in the browser console when you try to reply 16:34:57 Started with the 2.53.10.2, then updated to the 2.53.11 Beta 1, with same results. IMAP and SMTP server is set up. 16:36:36 (that is, opening the browser console (for this one you might need to use the browser window, it's in Tools->Web development), then doing the reply action and see if there is any new content in that console) 16:37:52 Timestamp: 17/02/2022, 17:35:52 CET 16:37:53 Error: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIEditorStyleSheets.addOverrideStyleSheet] 16:37:55 Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js 16:37:56 Line: 1594 16:41:00 Sorry about that, I could deduce that the theme I am using is causing this. 16:41:17 Changing to the default theme solved the problem... Sadly, not what I was hoping for. 16:44:03 builtin theme or a third-party one? 16:46:08 Third party. Orthodox 16:52:15 I should be already running the .11b1 beta 16:52:37 maybe the GiggityHub user menu bug with JustOff's addon is version-specific? A/B testing, missing polyfill feature, etc.... 17:04:11 https://github.com/JustOff/github-wc-polyfill/issues/44 iiiiiinteresting 17:04:29 a single menu breaks with the polyfill update, but only in SeaMonkey 17:04:42 FWIW, I just tested on .11b1, no change 17:04:45 tomman: besides perhaps runing that there are also patches in my 12b1pre builds that will be in 2.53.11 release if users who test say they work to fix something and don't cause any other issues. so if an issue een in te beta, if it is fixed in 2.53.12b1b1pre, that is useful information. 17:06:11 also, GitHub in general is becoming more and more unusable with each "shiny tech" platform update :/ 17:06:22 do those folks at GH/MS even dogfood their own crap!? 17:07:50 I am working hard to get my builds to be more useful. If you get them form the link to latest-253 link form the page referenced here they are onl posted there if all 7 builds are at least successful 17:08:32 WG9s_: worth a shot, I'll check out those now. 17:08:40 so that means all 5 platforms and 2 extra because windows installer and windows zip 17:09:31 thankfully I'm now testing on my spare laptop where I can blow up my profile at will~ 17:09:37 not saying you shoud try use ing them as default browser but doing a side by size installation to see if they fix your issue. 17:10:55 the production resources we have are kind of limited so uisng mh server to build some things with a test patch for a soingle issue 17:11:11 rahter than doing a beta 2 build 17:13:18 but some of what is posted on my server do not even build on all platforms so the ones on the link in the topic at least have successful builds on all platforms 17:14:59 and this is why I have extra metal, solely for testing 17:15:28 thankfully I won't be messing with my daily driver, but I'm not afraid of testing on a separate setup which basically mirrors my main one (except for hardware specs) 17:16:30 In other news, I can't follow the logic of this web design "paradigm": 17:16:42 have a page with a bunch of static elements, including a menu 17:16:43 So the ones i would test if you go to the link in topic and them click on comm-253-latest and that will get you to the latest version with no build issues on any platform. 17:16:52 but... don't build the menu on the actual HTML 17:17:03 instead request the menu over AJAX on load time 17:17:13 a STATIC menu that won't change for any logged in user 17:17:15 WHY 17:17:37 ah so trying something we just might not support yet 17:19:50 JustOff's polyfill is supposed to include the relevant junk to please GH, and indeed everything seems to work fine for Pale Moon users, but not on SeaMonkey 17:20:20 so telling if it is a browser bug, or just a polyfill flaw becomes tough 17:20:22 tomman you have t understand, our initial codebase is from June of 2017. THis that did not work then might be a rech to get to work now. 17:20:55 tomman you have t understand, our initial codebase is from June of 2017. Things that did not work then might be a reach to get to work now. 17:21:23 WG9s_ this specific GH breakage (user menu) is new 17:21:36 it started happening today because they went all in with shadowRoot 17:23:28 Oh well then pardon my interuption! (apologies to Larry David) 17:24:34 ...no luck either with 2.53.12b1pre either :/ 17:24:45 the menu still comes up blank even with the polyfills 17:25:36 was this showing some error in the page console? 17:26:06 or wait, the cause was already identified? I haven't checked the github issue yet 17:26:14 njsg: https://github.com/JustOff/github-wc-polyfill/issues/44 17:26:37 also, GiggityHub's had already booted off all non-ECMAScript 2020 browsers starting today 17:27:04 In any case, JustOff's addon update addresses almost all of the stuff, except for the user menu 17:27:10 but only on SeaMonkey 17:27:55 previous to the latest update, the error we were getting was "this.attachShadow is not a function" because of obvious reasons 17:29:25 (and it broke a bunch of stuff, including dropdown menus, the editor, and more) 17:29:35 even the github frontpage is being quite heavy and slow here 17:29:36 --GitHub, not the addon 17:29:53 well, with the latest addon update, GH more or less works, but some parts are indeed slooooooooooow 17:30:27 I'd guess the problem to be with the front page animation, but it might be something else. 17:32:00 "We design GitHub to support the latest web browsers." 17:32:09 reminds me of a comment I read earlier this morning on HN 17:35:18 Some stuff is already in 2.53.11b1 and more in 2.53.12b1 pre so this might be the problem. Still not working without stylo and a bunch of other stuff of course. I am using Credge for the junk gitlab and github pages. As long as command line git works I don't care much. They won't get a dime from me and can "enhance" till they are turning blue for all I care. When they want to charge me one... 17:35:19 ...day for nonexisting services I am out. 18:21:35 The child_process.exec(...) statement on an add-on runs nothing. Is it blocked on SeaMonkey? 18:22:02 I'm trying to debug an add-on. It simply does not call any command. 18:26:10 Sorry for the constant disconnects, but I managed to fix my problem. the messageQuotes.css was/is missing from the Orthodox theme. I downloaded the one used from XPFE-Classic and added it to the archive under the messenger directory, and it works. 18:35:43 oh, forgot the HN comment: https://news.ycombinator.com/item?id=30371606 18:36:04 "tech is already bloated, why bother using anything that isn't the latest shiny?!" 18:36:24 "Why continue to develop the older API while a new one is already underway?" 18:36:48 why bother buying a computer if someone is coming up with a new computer tomorrow? 19:23:18 why bother going to school? 19:23:41 (now that's probably a way to start an interesting thread in HN, and I wonder if somebody did it already) 19:23:44 * njsg opens link 19:41:09 why bother the enhance a "standard" when you can define a new one. 21:56:39 oh wow, GitLab also shat the pants on SeaMonkey, again :/ 21:56:50 "SyntaxError: invalid regexp group" 21:56:50 what did they do ? 21:56:54 don't wanna know... 21:57:08 even with JustOff's addon, the whole site broke again 21:57:34 it's like I have never installed the addon 21:57:47 which means the GitLab assumes I'm using Chrome™ 21:59:20 the stupid regex of the day: /^(?\s*)(?((?[*+-])|(?\d+\.))( \[([x ])\])?\s)(?.)?/ 22:00:11 named capture groups :/ 22:00:49 must be a miserable Thursday for JustOff, as I'm about to report this one too... 22:02:47 we all should move back to SourceForge 22:10:58 https://github.com/JustOff/github-wc-polyfill/issues/45 two in one day 22:19:54 tomman Need to get into the regexp issue. Fixed for Waterfox but wanted to do other things first. 23:11:43 GitHub user menu (top-right corner after login) works with github-wc-polyfill 1.2.12, but with seamonkey <= 2.53.9.1 23:12:18 Since seamonkey >= 2.53.10, the user menu is broken again (with the same version of the addon, ie. the latest 1.2.12). 23:12:21 Any ideas? 23:15:26 report the bug to M$ since they own github 23:18:54 I would like first to ask people, who should know what was changed between 2.53.9.1 and 2.53.10 :) 23:19:47 And it could be fine if anybody can confirm this too. 23:20:58 buc too much to pin it down. 23:22:35 frg: Maybe some nightly builds saved?.. 23:23:49 buc: http://archive.mozilla.org/pub/seamonkey/nightly/ 23:23:50 Anyway, is it at least reproducible? (ie. 2.53.9.1 OK, 2.53.10 not)? 23:25:02 Afaik not for CentOS-7 :( 23:25:25 2.53.12 now has basically all 57 patches minus a few bad ones for feature removals and bad taste applied. 2.53.10 was well into it already. 23:25:38 Maybe https://archive.mozilla.org/pub/seamonkey/nightly/2021/ 23:26:20 It should be something under "js/src" I believe. Before I start to track -- does anybody pls comfirm the issue? 23:26:39 (I mean check it under 2.53.9.1 and 2.53.10) 23:28:35 buc modules/parser and the legacy generator/version removals from content (which probably broke add-ons too) are the biggest changes there I think. 23:38:27 I can check but don't have an account. From the issue seems to be only a problem when logged in? 23:39:03 Talk of bad code: 23:39:04 Warning: Expected a percentage but found ‘calc(’. Error in parsing value for ‘border-color’ after substituting variables. Generated value was ‘hsla(353, calc(66 * 1%), calc((53 - 25) * 1%), max(0, min(calc(( calc( ((215 * 0.2126) + (58 * 0.7152) + (74 * 0.0722)) / 255 ) - 0.96) * 100), 1)))’. Falling back to ‘initial’. 23:39:06 Source File: https://github.githubassets.com/assets/behaviors-8f389ba0b0ad6af7801f6fb174d40991.css 23:43:42 Just a warning: if you're using github-wc-polyfill adddon 1.2.12, expect MASSIVE SLOWDOWNS on GH 23:44:23 1.2.11 doesn't have them, but it's also kinda useless due to the site breakages 23:45:54 frg: "Expected a percentage but found ‘calc(’." -- it is with 2.53.9.1 (which works) too. 23:46:32 tomman: Can you reproduce the 2.53.9.1 vs. 2.53.10 difference on 1.2.12? 23:47:08 buc: will test that 23:47:32 buc was just a warning. This calc syntax is not implemented. 23:48:34 But what idiot uses such complex calculations in css for forking colors? 23:53:40 If anyone can pinpoint it to a date range with the available nightlies from WG9s I can check the patch queue. 23:59:32 tomman: There is only one commit for github-wc-polyfill-1.2.12 -- maybe indent the code (as usual :) ) and try to bisect something.