12:02:37 * IanN_Away wonders if anyone is building successfully against gcc 11 libraries 13:30:10 Status meeting starts in 30 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-09-19 13:40:10 IanN: Normally, I compile with clang 13:40:44 I have now tried compiling with gcc 11.1.0 and it worked. 13:40:50 (for Arch Linux) 13:41:20 Hi teruna 13:41:54 In the blfs manual they also mention gcc. 13:42:31 Hi frg 13:45:41 BTW, using rust 1.55 works too. 13:46:29 teruna: hmmm, I'm trying on fedora 34 and no luck with building 13:46:52 teruna: using clang 9.0.1 13:47:48 Arch Linux is already at clang 12.0.1. 13:48:55 Status meeting starts in 12 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-09-19 13:52:02 I might try with clang 12.0.1 instead 13:55:17 Status meeting starts in 5 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-09-19 13:56:04 hi WaltS48 13:56:31 Hi IanN and others. :) 13:57:33 Hi WaltS48 13:58:32 hi rsx11m 13:58:52 hi IanN frg WaltS48 13:59:03 Hi rsx11m 13:59:21 Hi rsx11m, frg 14:00:21 Status meeting time - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-09-19 14:00:46 Who's taking minutes? 14:00:51 me do 14:01:02 thanks frg 14:01:11 Nominees for Friends of the Fish Tank? 14:01:41 frg for his work on general and security backports 14:02:09 abstained :) 14:02:55 * IanN looks as rsx11m 14:03:05 * rsx11m is always seconding 14:03:27 thanks 14:03:58 Action Items? 14:04:53 no change as far as I am aware 14:04:56 Nothing new from me. 14:05:29 Status of the SeaMonkey Infrastructure 14:05:40 It is either website or code and code won again in the last 2 weeks. Plus support. 14:06:23 Nothing directly from me. VS2022 preview 4 tested against latest 2.53.10 so should be a smooth ride on the builder later. 14:06:51 Current VS2019 and rust 1.55 are ok too for 2.53. 14:08:34 switching to gcc-8 for i686 builds 14:08:46 (on linux) 14:09:15 meeting time, nice~ 14:09:16 hi guys 14:09:25 Allows to use c++ 17 fatures needed for later ports like the new regexp. Should uncork some web compatibility problems when done. 14:09:31 Hi tomman 14:09:51 it was gcc-6 14:09:56 and from clang8 to clang9 for macOS cross-compile 14:10:11 Just tested the resulting clang 9 build for macOS and it is fine. 14:10:57 ewong is still testing the crash reporter 14:11:20 still good until the end of October... 14:12:36 yeah, we will be switching in 2.53.10 14:13:50 will "ours" be for us only or would it include Thunderbird as well? 14:14:10 rsx11m: just for SM 14:14:21 rsx11m ours. Relations with TB are mostly severed unless I am wrong. 14:14:29 ok... 14:14:39 And it is not us :) 14:14:54 * rsx11m didn't imply that 8-) 14:16:10 Status of the SeaMonkey Source Tree 14:17:35 I believe everything is building 14:17:46 All building I think. Please test the latest 2.53.10b1 pre. I backported some parser changes and they might break things. Broke Downlaod them All for sure but this needs to be updated. 14:18:16 Easy one in a few places Bug 1228841 so you can do it yourself. 14:18:42 DidnÄt have time for 2.57 again sigh.. 14:20:15 also there is now a in 2.53.10b1 pre, so test it has not broken anything 14:20:48 bug 1730392 14:21:54 input field date now works in 2.53.10b1 pre but still needs some styling for Modern. time works too but is prefed off (as in latest Fx) 14:26:07 what is that pref? 14:26:39 dom.forms.datetime.timepicker 14:27:40 thanks 14:27:42 Next goal will be intl.locale and datetime stuff but first things first. 14:27:42 Release Train 14:28:08 We will do a 2.53.9.1 14:28:33 ESR78.14 backports, a few crash fixes and a regression fix for images not displaying. 14:28:49 Also switch the default font to sans-serif for mail 14:30:16 2.53.x.1 releases are becoming routine, eh? 14:30:30 https://ibb.co/dKryPVW (visible till tomorrow) for a preliminary bug list. 14:31:09 2.53.10 has so much new stuff and is still missing l10n translations so better to get some fixes out. 14:31:18 makes sense then 14:31:54 And the betas (including pre builds) are not tested enough it seems or the image bug would not have crept in. 14:36:00 Extensions Tracking 14:36:57 cZ gets the most love right now. JustOff updated the polyfill for github and gitlab. 14:37:07 github-wc-polyfill is now up to 1.2.4 14:37:19 https://github.com/JustOff/github-wc-polyfill/ 14:38:14 We are only using gitlab as a repo basically so no big loss when they break us as long as command line git works. 14:38:29 we would still rather they didn't 14:39:13 2.Next, Feature List, Planning and Roundtable 14:39:30 Well they don't care about "minority" browsers. As loang as they are free I don't care if they don't care. 14:40:02 The usual bau from me. 14:40:26 Ditto 14:41:18 And a message to people telling us the we have web compatibility problems: We know and if you want to help out fixing them you are welcome. 14:46:17 AOB? 14:46:39 bau 14:48:15 next meeting is in 2 weeks time 14:48:25 see you in October! 14:48:29 same bat time, same bat channel 14:48:52 thanks for your time today 14:49:15 bye 14:49:23 c u rsx11m 14:49:58 bye all and still here :) 14:50:20 teruna: the build process seems to be working so far with clang 12.0.1 - thanks :) 14:57:23 see in the next meeting~ 14:57:45 frg_Away: love that message, but I would send it to webdevs instead 14:57:54 they're the ones causing all of us this pain 15:03:19 tomman well one against the world will do us no good. And while I "disagree" with a lot of the new stuff and the direction all this is heading there is still a need for updating specs and language. Some things like the optional chaing operator are actuall quite useful. As I always say a browser is not a museum :) 15:47:25 IanN: Good to hear. :-) 16:32:40 frg_Away: gonna steal that phrase~ 16:35:44 https://github.com/dothq/browser I thought Gecko-based browsers were dead, nice to see some competition 16:35:49 ...but then 16:36:50 why using emojis on nearly every single git commit!? 16:58:20 tomman these are usually one man/woman/martian forks either not deviating much from the mainline or dead in a month. 16:59:18 I'm not gonna use it (braindamaged UI is still there), but the last thing the world need is yet another Chrome skin 16:59:31 hope it lasts for some time 17:02:21 ...still wondering why there is absolutely zero coverage of SeaMonkey on Hackernews 17:02:50 even Pale Moon gets mentioned once in a blue moon (with the same obnoxious "it's old, hence it's UNSAAAAAFE!!!" snarky remarks) 17:03:23 the comments on this browser are sadly not that different: https://news.ycombinator.com/item?id=28584630 17:16:47 web developers actually telling explicitly which features they need or at least having unobfuscated code that can be debugged is of course better than some cases I've seen 17:18:07 when you serve a pile of spaghetti that errors out somewhere in line one and that is full of unreadability layers, it becomes a lot more difficult to identify the problem 17:18:54 s@the problem@problems@ 17:21:13 njsg: they will claim that serving unobfuscated code kills performance, wastes bandwidth (that costs money), and even exposes them to the risk of intellectual property theft 17:22:00 which, while being valid reasons, are still lame excuses to not getting involved with web browser development 19:59:38 how do i change the start page? 20:01:32 Walter: Edit->Preferences->Browser 20:01:37 oh~