Did the latest stable fix the Publish window not closing after publishing ? Yes, I've unticked the box.

I suppose the screenshot from bug 1112694 illustrates that problem as well?

"all files published" and the checkbox is not checked

something like Do you wish to end the hold and resume the schedule?

this is a taking questions that have a yes/no answer but then displahying buttons that say cancel and conform or any other working should just be yes or no.

oops thos last 2 posassts ers intended to be in the conversation with njsg

Status meeting starts in 29 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-02-20

Hi tonymec

hi frg

hi tonymec, how were the storms for you?

next one due tonight I think

hi IanN, with a heavy coat I could stand them, and you?

Hi everyone here for the meeting

Hello!

hi lonely one here for the meeting :-P

Hi jardsonto

Hi WaltS48

Hi frg, WG9s, IanN and all.

tonymec found it not so bad. Coast was hit harder but nothing I haven't seen before. Was a bit surpised that this one was categorized as the worst since 2007.

hi WaltS48

frg: hm, maybe we weren't outside in the worst of it.

hi WaltS48

tonymec: got soaked

IanN no hiking in the woods I assume :)

frg: not this weekend

IanN: here in Brussels I felt more wind than rain.

IanN looking at the forcast does not look good for GB the whole week depending where you live.

west coast might get it again harder.

here where I live in massachusetts sometimes storms that don;t seem that bad to me are thought to be the worst becuase of the number of beachfront proerties that got totalled. but then some of these seem to be build between where the lighthose is and the waters edge so seems to me the fault of any one who build bought approved a mortgage or insured issue as being just terminally stupid.

WG9s they started to build houses in known natural areas subject to flooding here and then guess what happend when the flimsy levees they added to the areas broke...

but really building closer to the wate rthan the lighthouse? that just seems like recipe for disaster.

Status meeting starts in 5 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-02-20

WG9s: depends... I know places with a lighthouse at the back of the harbour entrance channel and another one higher and further back, blinking isophase to create an alignment.

hi rsx11m

hi IanN frg tonymec WG9s

hi rsx11m

Hi rsx11m

hi .*

It is not everywhere in the sate. People on the NOrth Shore have lost homes that were there forever, but we have these pople on our south shore who had money could pay off people to get permission to build where they should not have been and got what they deserved.

hi njsg

hi rsx11m

Status meeting time - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-02-20

Who's taking minutes?

me and probably late again

Almost forgot last time because didn't add it to my virtual post-it.

so you mean late posting

Nominees for Friends of the Fish Tank?

WG9s: in the Netherlands there are several "verdronken landen" — areas of several villages each, which were drowned by tidal storms in the Middle Ages and are still under water.

Nominate WG9s for building our prereleases and central and keeping up with my/our doings with the patch queues.

second WG9s

Well thank you

3rded

Action Items

Nothing new from me.

I am still remiss in not getting my promised logbot working

Status of the SeaMonkey Infrastructure

i do have the disk frg provided installed and it is bing backed up now so just neet to catully do the part where it logs in and logs

All building I think. I worked a bit on further stylo updates for later rust versions than 1.37 but got bogged down quickly with rust dependencies.

Rest assured will never be my favorite language.

nor rust :P

hmm need to update the reomving 32-bit support to say 2022 rahter than 2021

... didn't happen in 2021, apparently ;-)

Windows x86 still builds fine and so does Linux for now. Can keep it but don't expect me to give much support for it :)

Maybe ewong can get some numbers from the update server?

we are hoping to enable heptapod hg repos soon

Status of the SeaMonkey Source Tree

For the infra I might update the VS2019 for the final release. They fixed a compiler bug in it and seems to do fine.

VS2022 17.1 is usuable too now but I intend to keep VS2019 a while longer.

frg: sorry jumped the gun

For source tree have some work in progress stylo updates for 2.57 but nothing more for it. Still backburner. 2.53 is progressing nicely.

my builds still use vs2019 becuase i am still keeping vs2017 around just in case need to do something with a new SeaMonkey 2.49 security update and keeping 3 version of VS around is a bit much.

also 32-boit supoort I might be able to find time to keep them at least buildsng if frg gives up on them.

WG9s well basically you use clang and the VS2019 tools only :)

yes

But VS2019 can be used with 2.49. You need to install the VS2017 toolset and XP dependency stuff.

MOzilla no longer builds uisng MSVC and so I d not either. even for 2.53

Yes Thought about switching but I like to have two compilers around for testing and debugging.

plus otheres might want to build and debug using VisualStudio

in the gui

I think it is supported now with clang too because MS bundles it.

Release Train

2.53.11 is late but building should begin today. Checking in the patches right now.

2.53.11 should be released in the next week

If any latge breaking patches show up let me know and I can include in my builds

late breaking

WG9s don't think so. A few sec fixes and also found a few crash fixes for mail which are included. Already in your builds to see if they are bad. No complaints so in they go.

Also the TrimStart and TrimEnd string properties discussed two days ago.

yes was asking if something shows up not yet in mhy builds feel free to aks for me to do an eraly build if required

WG9s nope all in and expect anything else.

fyi gitlab 2.53.11 final branch is now updated.

So the build fun can start

Extensions Tracking

I removed a few more NPAPI bits in 2.53.12b1 pre and also started to take out gtk2 which is dependent on this.

github-wc-polyfill is now at 1.2.13

Closed Bug 1367257. If anyone objects reopen :)

github still has problems with it but seem to be css related. gitlab seems to do better and heptapod is now supported too but didn't check.

i like that I worked wth the redhat people on trying to get firefox working with gtk3. I have no idea why we would need to still support gtk2.

WG9s we don't but the NPAPI stuff is still in and needs it for building.

2.Next, Feature List, Planning and Roundtable

Bug 1675349 and Bug 1682030 are needed. these are 40 parts and there are only so much hours in the day :)

no worries ...

Tried just putting Bug 1377445 and followups in but this breaks.

for roundtable I am still working on geting an irc logbot and server set up. just seems not enough hours in the day!

I got a new job starting in May so this will impact my availablity unfortunately.

BAU for me

i do have a new drive set up for the data and mhy backup set up to back it up so now just get the config files working and things being logged and having a mechanism to make one of the channels I want to backup be private with logins required.

bjt I could start with out backing that chennl up

Doing robin round with backports. Now on microtasks but not sure if I can put them in fast.

problem with the one channel trying to keep private is trying to design a way to permit people via the webserver to change their password

But 2.53 is now beyond 57 level with base fixes and while this still sounds outdated the big reshuffles in the source done between 56 and 57 make applying follow-up patches easier.

I had a look at some Composer issues, I hope I can do something to add error handling and error messages to the save code; there's at least one bug about slowdown in source view but that seems to be from the editor element, when it is filled with a long-enough multiline text

AOB?

not here

neither nere

okay, next meeting in 2 weeks time, same bat time, same bat channel

see you in March!

bye

bye

bye

see ya

bye rsx11m and tonymec|away

bye walts48

see you

hey, I wanted to say i found a minor problem with the README that gets generated for seamonkey releases

it says the command 'git clone -b 2_53_10_2_final gitlab.com/seamonkey-project/seamonkey-2.53.10-comm.git comm-25310' was used to get the sources for 2.53.10, but that git repo doesn't exist

(or is not public)

gitlab.com/seamonkey-project/seamonkey-2.53.10-comm.git -> gitlab.com/seamonkey-project/seamonkey-2.53-comm.git

in other words 's/\.10//'

i am referring to this file btw archive.mozilla.org/pub/seamonkey/releases/2.53.10.2/README.txt

Well, the issue with "user-menu" with github-ws-polyfill-1.2.12 and SeaMonkey >= 2.53.10 seems to be introduced after the backport of bug 1391154

See wg9s.com/comm-253/patches/seamonkey…-release/patches/1391154-61a1.patch for more info.

Any thoughts are appreiated.

tomman: If you wisely have not begun to bisect yet, then do not do it. :)

After reverting bug 1391154, the "user menu" works under 2.53.11b1 (with both versions of the github-wc-polyfill addon 1.2.12 and 1.2.13)

buc: haven't had time to figure out where I do even start, but nice to hear that there is actually a regression

or something

"This matches Chrome's implementation and the tests."

once again, I died inside

tomman: They seem changed algorithm while going to use IndexOfFirstElementGt(), need to check a bit more to explain.

Hmm even with the patch the test seems flaky but less flaky: jsfiddle.net/8f9whxbk/11

Oh wrong test. belongs to Bug 1505471 which is not in.

i'm sure this is a common question, but i checked out the source repos and am trying to build seamonkey 2.53.10 from them. I am running './mozilla/mach build' but it doesn't seem to be using my mozconfig (which has ac_add_options --disable-pulseaudio specified).

additionally config.log is going in the mozilla/ subdir's object path instead of the MOZ_OBJDIR specified in the mozconfig

do i need to be doing something else first?

or do i just have my dirs inverted

wyatt8740 Yes inverted. The mozilla source is now the top source dir. The suite/mail code is now in comm under it. so you just use mach build. The final 2.53.11 code is now in gitlab and you can check out this branch. Lots of internal fixes/backports over 2.53.10.2

buc I just added 1505471-68a1.patch to gitlab. The reported coordinates are now correct but I doubt it will help with the problem. Worth a try if the menu uses an intersection observer and relies on the coordinates. But probably not because not an iframe.

Well, commenting out "if (threshold == 0) threshold = -1;" in the bug's 1391154 patch resolves this issue.

The correspond comment in the patch says: "Per the spec, we should leave threshold at 0 and distinguish between "less than all thresholds and intersecting" and "not intersecting" (queuing observer entries as both cases come to pass). However, neither Chrome nor the WPT tests expect this behavior, so treat these two cases as one."

So, if we start to treat it as "per the spec" (instead of per Chrome), the issue gone.

There are no any changes here in the current Firefox code tree (but this mean nothing - the current Fx development has long ceased to be the ultimate truth).

buc yeah but if I read it right it is done to match Chromes behaviour: [User impact if declined]: IntersectionObservers' behavior would not match Chrome's.

See comment 47

frg: Unfortunately, bug 1505471 itself does not help the issue.

buc thought so. Was worth a try. I think I remove the per the spec line as you suggested in a separate TOP patch so that it works for now.

a bit late for 2.53.11 unfortunately.

buc as a last shot can you try with 1711050-nsrefreshdriveroptimize-2538.patch removed.

2.53.8 < 2.53.10 ... :)

buc I know. But just want to make sure that this is not causing it and that it worked by accident or because of the unfixed bug before. Should not be a chrome uri thou.

is this testable without needing to log in?

No. :(

1.2.14b1 fixed the load diff css problem btw.

Added TOP-9999999-fixgithubpolyfill-25312.patch to gitlab 2.53. Will file a bug against 2.53.12 / our mozilla branch if we do not find a better solution.

OK, LGTM

frg_away: thanks

I'm testing building for ppc32 linux though so I figured a release might be a little more trustworthy when trying to iron out problems

haven't done one of these cross builds since 2018

buc thanks for tracking it down.

wyatt8740 is rust available for this arch?

frg_away: yeah, RUSTFLAGS=--target=powerpc-unknown-linux-gnu

the showstopper for firefox itself is node.js/V8 in the build system

frg_Away: is rust available on OS/2?

IanN_Away no. I still wish they would release the OS/2 source but probably lost. Decommisoned my main OS/2 system and moved it into a vm. But still have it on a T42p.

rustc --print target-list

ooh, talking os/2? I have boxed shrinkwrapped CD copies of the 3.0 connect bundle, both red and blue spines

i think the only machine i might be able to get it running on is my thinkpad 350 or _maybe_ a latitude D610

due to overall lack of experience

IBM s*cks. The managers are the Dinos not the older employees and should be made redundant. They ruined everything. PS/2 MCA, token ring, Thinkpads, DB2 and now on the last leg with z/OS. Seeing migration projects left and right here. Could possibly make a fortune if I would turn myself into a consultant for these.

i wish i had the knowledge to do AS/400 programming, there's an opening in town right now

would be good money for a while

hmm, nspr is throwing up errors from 'as' while building. how do i get more details (like the invocation?)

wyatt8740 Did mostly OS/390 z/OS. PL/I TSO IMS DB2 CTRL-M and TELON generator. I still love PL/I

mach build -v ?

ah, d'oh

still used to make -f client.mk

haha, that's funny

i think this is happening because it's trying to use -fPIC

Needs NASM and still YASM. Might need to convice Bill to port the patches needed to kick out yasm :)

wasn't nasm x86-only? or am i forgetting everything again

I only really do assembly on the 68k

Don't know. Will find out if I find the time for doing patches to allow for mac or Windows arm builds. Probably mac first.

hmmm. i have no idea where it's even getting -fPIC from

not entirely unheard of apparently mozilla/nixpkgs-mozilla #278

too bad the explanation doesn't make sense to me

ah, thanks grep. `old-configure: ASFLAGS="$ASFLAGS -fPIC"`

` 0:01.40 Fatal error: invalid listing option `,'`

still got work to do i guess

frg: sent you an email with better fix.

A time to open a bug I believe :)