SeaMonkey/StatusMeetings/2024-03-24

From MozillaWiki
Jump to: navigation, search

« last meeting | index | next meeting »

SeaMonkey Meeting Details


Agenda

  • Who's taking minutes? -> frg
  • Nominees for Friends of the Fish Tank:
    • IanN man of the meeting

Action Items

(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.

NEW

  • —

OPEN

  • KaiRo has sent all available svg and SeaMonkey image data to IanN and frg.
    • We need to find a permanent place for them to make them available at least to the core developers outside of the source tree.
  • We want to create a gitlab patch/fixes repo for classic XUL extensions.
    • IanN is looking into it.
  • Mozilla finally decided to fully cut us loose in Q3. Formally and legally this is all in order.
    • Source code will probably be removed from comm-central because it seems parts of MZLA and/or the Thunderbird council are eager to do the same.
    • Fortunately we are mostly independent already and it will not affect the 2.53 line or building releases.
      • Depending on when this will happen we will have a delayed release and maybe broken updates for one release too.
    • If this happens it is unlikely we will pursue upstream fixes for suite any longer and just concentrate on the 2.53 fork
    • We need to find replacements for bugzilla, translations via Pontoon, add-on and the distribution site.
      • Reviews for SeaMonkey add-ons seem to no longer be done anyway. We don't have any access there.
    • We are currently evaluating options together with Mozilla.
      • Source code, Pontoon translations and Bugzilla are the three items we would like to keep as is. Needs to be decided higher up at Mozilla.
      • We got a preliminary approval note to extend our stay on the other Mozilla infrastructure till the end of 2024 but need to formalize some things till then.
  • Fix website for google group changes.
    • Dev group was discontinued and the SeaMonkey support list is more or less on life support.

CLOSED

  • —

Status of the SeaMonkey Infrastructure

  • Our infrastructure is using Azure.
    • ewong has been looking at Kallithea, RhodeCode and other similar tools which are needed later to automate source code management for non mozilla repos (tools, website and others).
      • Also evaluation of Ansible and Terraform going together with it is done.
    • Jenkins is being set up on the builders.
      • ewong is making progress setting up automated build jobs using it. This will still take some time.
    • Cloning the mozilla- repos is problematic. They are huge and the process is slow.
      • Incremental updates need to be done whenever possible later.
  • Please see Infrastructure Status
  • IanN has started updated the in-tree config files in bug 1687385
  • Mozilla switched Windows builds to cross compile on Linux.
    • This would need backports but is not 100% native (needs Wine). So currently no plans to do this for SeaMonkey.
    • Discussion for later when setting up jenkins. Even buildbot had some version specific files outside the tree.
  • Some Capacity planning to find the best price/performance ratio is carried out.
    • Other than azure hosting options because of price are also evaluated.
    • ewong set up the downloads archive in our Azure CDN for now.
  • We now use our own breakpad server for submitting crash reports.
  • We moved to bugsplat.com for crash reports with 2.53.18b1
    • We currently are not generating crash reporter symbols for macOS releases.
    • This might not get fixed soon because it needs a new builder and more fixes in the source tree for later clang and rust versions.
    • frg tried locally in a Rocky 8 vm and the generated symbols turned out to be incomplete.
  • The WGS9s servers are working fine and unofficial builds are being released.
  • We have created repos at hg heptapod to mirror some of our code.
    • Mirroring between gitlab and heptapod is being discussed.
    • The website code is now maintained on heptapod.
      • We no longer mirror the website in hg.mozilla.org and might stop this for gitlab too.
    • Mozilla plans to move to github and abandon mercurial. We have no plans to do this for our release branch and the website.
      • This might affect future checkins into comm-central.
  • frg proposes to end 32 bit release support in 2024. Main reason is that modern websites are memory hungry and the 32 bit only architecture cause more and more oom crashes and subsequent complaints. Mozilla recently stopped testing Linux x86 releases too.
    • No consensus reached about it yet. So far building it is possible with gcc 8.3.1 under CentOS 7 and clang under Windows.
  • To reduce the use of different compilers we are looking into compiling future 2.53 Windows releases with clang 14 or later.
    • Currently CentOS 7 can not use the mozilla provided compilers because of a downlevel libstdc.
  • VS2022 is theoretically supported but building is currently broken because of compiler changes.
    • The Windows build server will and can not be switched to it for now.
  • The latest Windows 10 toolkit 10.0.20348 for Server 2022 causes a compile error with the mapi.h header.
    • Recommended version is still 10.0.19041.
    • The Windows 11 toolkits 10.0.22xxx.x can also be used. The MAPI header was fixed by Microsoft in them.
  • Preliminary aarch64 support for Linux has been added to 2.53.x
    • Native arm support for macOS and Windows is looked into for a later date.
  • We plan to update builders with 2.53.18 but might need to be delayed for another release.
    • CentOS 7 reaches EOL in 2024.
    • ewong has set up a Rocky 8 and Server 2019 builder.
      • Fixing the macOS build symbols issue, later compiler support and fixing the native macOS build can now be tackled.
      • The minimum libstdc++ will change with 2.53.18 to the current Mozilla Firefox level.
      • EOL for 2012 R2 is 2023 but has been extended in Azure.
    • We might switch to dedicated builders later because of cost savings and better performance.
  • For Windows mozbuild 3.4 is working.
    • Mozbuild 4.x is currently broken for building 2.53.x because of msys2.
  • Mozilla l10n will move to github soon.
    • TB staff will not migrate suite l10n so we need to find a solution for our translations.
    • We have mno plans to move 2.53 development to git. Mercurial suites us well.
    • gitlab source is used for releases and holding the patches queues only.

Fixed Infrastructure Stuff Since Last Meeting

  • —

Status of the SeaMonkey Source Tree

  • Useful Firefox Release Schedule link: Releases Scheduling
    • Last Merges: March 18th, 2024
    • Next Merges: April 15th, 2024
    • SeaMonkey is now at version 2.123a1 on central. Gecko is at version 126 after last merge.

[comm-release56]

  • The 2.53.x development builds are based on the last 56 release changesets in our heptapod comm-release and mozilla-release repos.
  • Building stylo and webrender is currently broken but disabled by default.
  • Rust 1.61+ is needed for building. We recommend 1.73.0.
  • Rust 1.74 and up will not be used for building official releases as of now because we still support macOS 10.11.
  • 2.53.17b1 and up no longer need Python 2 for building. There is still some breakage in test code and other areas because of this.
    • Breakage and support for later Python 3 versions will be addressed as fast as possible.
  • l10n translations are not 100% complete for some languages. If you notice missing translations in your language consider opening an account on pontoon and help with translation.
    • The site is incompatible with SeaMonkey up to 2.53.17.1 so you need a different browser for this.
  • Compiler support is up to date.
    • clang 6 to 15, gcc 7.1 to 11 can be used to build on Linux or clang only for macOS.
      • clang 15 and higher is currently not supported with macOS builds if you enable crash reporting.
      • clang 16 and hight might work but have not been tested yet.
      • macOS sdk 13 or higher can currently not be used. The binary will not start because of some linkage issue if you do.
    • macOS arm builds are still not possible amd would need to be notarized which means buying an Apple developer certificate at least.
    • clang 7 to 17, VS2017 15.9.13+ and VS2019 are supported under Windows x64.
    • VS2019 and VS2022 are currently not supported for compiling Windows x86.
    • VS2022 can currently not be used for compiling Windows x64. New features in it need fixes in the source.
    • Support for clang 6 will be removed. The new regexp parser needs full c++17 support. Currently we worked around it but while this may work with clang 5 and 6 it is basically untested.
    • Mozilla skipped clang 10 support because of unspecified problems and did go straight to clang 11 from 9. We will not support clang 10 either. It can be used but is unsupported by us. gcc 9 and up did not get much/any testing so ymmv.
  • The latest macOS sdk is now supported in 2.53.15b1 or later.
  • Native macOS builds are broken and need fixes which would break building on the CentOS 7 builder.
  • Current Firefox and Thunderbird only support macOS 10.14 or higher. We support macOS version 10.11 or higher.
  • Cross-Reference sources are available at SeaMonkey 2.53 current.
  • enable-elfhack does not work with clang and lld as linker under Linux.
  • They are no plans to drop macOS 10.11 to 10.14, Windows 7 or 8.1 x64 support.
    • Windows server 2008 R2 and later are also supported.
    • Running under Windows 8 or Server 2012 (original not R2) is not being tested by us.
    • Official Linux and Windows x86 releases might be phased out later.
  • The l10n master branches have been updated on heptapot and gitlab.
    • Unlike the 2.53 comm and mozilla repros we do not need to do backparts and can always update to the latest translations and just tag releases.
    • The l10n translations for the next release will be kept in the patch queue until it tagged for building and it s branch for the regluar fixes has been checked in.
    • frg tries to add support for later javascript syntax features in a separate wip patch queue. Progressing nicely and beyond 62a1 now.
      • Missing support for dynamic import, big int and private class fields are the top issues which need to be addressed.
  • See bug 1688498 for important current 2.53 issues and enhancement requests.

[comm-central]

  • Windows, macOS and Linux builds.
  • Do not try to use the comm-central release.
    • For building you need to apply the preliminary patches from our [https:// gitlab.com/frg/seamonkey-central-patches/ gitlab central patch queue].
      • Because of some components removal and internal changes building central is currently broken without them.
      • This will not give you a working suite.
      • The installer still works...
  • comm-central builds will no longer be published on the unofficial site.
  • bug 1611647 was filed for SeaMonkey to do the rename from xul to xhtml files and references.
    • It has been done but not been checked in yet because other checkins would need to be rebased constantly then.
  • See bug 1452448 for current comm-central issues. This is not up to date.
  • Thunderbird plans to check in their source as a branch in mozilla-central and drop the suite code.
    • We are evaluating options. Best would be to still have the source code in together with Thunderbird otherwise we would need to merge mozilla and Thunderbird changes into a new repo.
    • A unified repo will be slow and cumbersome to handle in any case.
    • This seems to be currently on hold.
  • If building fails because of a missing wasi-sysroot your need to add "ac_add_options --without-wasm-sandboxed-libraries" in the mozconfig.
    • You can also download the wasi-sysroot from wasi-sysroot manually.
  • l10n support for comm-central has moved to comm-l10n.
  • The l10n strings for Thunderbird and SeaMonkey are now in the comm-l10n repo.
    • This does not affect 2.53 builds which use back merged strings from the upstream l10n repos.
    • Patches for build breakage and new reviewed functionality in suite have been checked in.
    • mozilla plans to move to github. We expect MZLA to follow and need to evalutate later how central source updates can be done.
    • Tobin tries to get central updated to a point where SeaMonkey at lest shows a window so that we can do further work on it.


Release Train

SeaMonkey 2.53.x

open tracking (0) tracking requests (40) targeted (2) fixed (688)

  • We will release SeaMonkey 2.53.18.2 soon.
    • This will be mostly a security only release.
    • The release is tracked in bug 1885417.
    • The website update is tracked in bug 1885418.
  • The next beta SeaMonkey 2.53.19 beta 1 is delayed a bit.
    • There is no ETA yet. While the source has been updated extensively it is mostly groundwork which does not warrant a release yet.
    • We would like to address some web compatibility problems with this release. This takes a bit more time to do.
    • If an important security issue comes up it will be released fast or we will do 2.53.18.2.
    • Please help test the prerelease versions too.
  • Because of bad user agent sniffing we updated the base UA version some time ago from Gecko 68 to 91.
    • YouTube no longer seems to display correctly for some users only advertising Firefox in the UA.
    • Further enhancements are planned for a later release in bug 1737436.
    • We want to implement overrides for bad web sites like Waterfox does using a json file containing the UA replacements.
      • The Fedora maintainer already added some of this and we will likely use this in the official release.
  • Some languages might need new or more translators. See help wanted for translating.
  • frg proposes to skip beta releases because we get no or minimal feedback only and this delays delivering security fixes among other things.
    • No consensus reached about it yet so we will continue with the current release Beta/GA cycle.
  • NSS 3.49 and up drop the dbm compatibility module. This has been restored for 2.53.2. Later we might do a hard block upgrading from an older release.
    • Distributions using the system NSS might need to adjust compile settings for this.
  • The following bugs are not yet fixed in 2.53.x:
    • bug 1409458 "Privacy Issue: Replying to or forwarding an HTML e-mail with external content".
    • bug 1684651 SeaMonkey under later macOS versions does not repaint the scrollbar correctly on all sites.
  • A meta bug bug 1584728 tracks the rdf removal from SeaMonkey.
    • Old 2.53.x bugs are still marked as not fixed in bugzilla. We will mark them as fixed as time permits.
  • We are looking into adding full support for Custom Elements and Shadow DOM in a later release. No ETA yet.
    • What is there has been activated in the current release. Shadow DOM support is mostly still missing.
  • During mail archiving frg noticed that the maildb code might still have issues. Using the Import Export tools add-on not everything was initially exported and only after unsubscribing/subscribing to some imap folders again it worked.

General SeaMonkey release issues

  • Licensing issues and maybe adding additional licenses need to be discussed. Code from bug 1559900 to do this has been included in 2.53.
  • Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
  • In bug 1674946 it is proposed that setting security.enterprise_roots.enabled to true unconditionally should be done to avoid problems with thrid party firewalls and antivirus programs.
    • The general opinion is that the setting should be exposed in the preferences but not make the default.
  • Because of missing features some major websites are broken.
    • We are backporting new features and also updating the comm-central repo for a later releasd wich is up to date with current Firefox as time permits.
    • Non working websites should be verified against a genuine Firefox 56 and 60 before filing a bug.
      • If a website does not work in Firefox 60 it is either fundamentally broken or needs some later not yet implemented features. A web compatibility bug against SeaMonkey can be filed but don't expect fast or any progress.
      • If a website works in both 56 and 60 it is usually only problem with incorrect user agent sniffing. Bug should either be closed or moved to the tech evangelism component then if the triager does not think it is a problem with SeaMonkey implementation.
    • In any case problems with specific websites should be discussed in the support groups first.

Extensions Tracking

+ Possible breakage in 2.53.

    • Because of needed parser updates the legacy generator syntax, iterator and old array comprehension syntax was removed in 2.53.13b1 pre.
      • The add-on sdk still needs some fixes for this. Please check the prerelease for extension breakage.
    • bug 1388317, bug 1083458 and bug 1389510 were backported to 2.53. Please check and try to fix extensions still using these features. With this done backporting is much easier now.
    • bug 1374847 was backported to 2.53.17b1 pre and some extensions like prefbar need a simple fix.
      • nsIPrefBranch2 and nsIPrefBranchInternal needs to be changed to nsIPrefBranch.
  • Thunderbird did discontinue classic add-ons with the ESR78 based release.
    • Mozilla removed the last traces of classic add-ons from the Gecko source code. They can no longer be installed.
  • cZ was integrated into SeaMonkey in bug 1551033.
    • The language pack for cZ was removed for 2.53.8 and a translated cZ is included. SeaMonkey language packs will now support cZ too and translate it.
    • The current cZ source code was checked in without history into comm-central. History is available in our 2.53 repo and current patch queues.
    • cZ is no longer an extension in comm-central and fully integrated.
    • Starting with 2.53.10 cZ is made available in all our shipped languages.
    • Some translations are still incomplete and will be updated continuously with the latest l10n changes from upstream.
    • cZ has gotten many enhancements in 2.53.9b1 and 2.53.10b1. Read the release notes.
      • Better SASL support and enhancements for storing the passwords are in 2.53.10b1.
  • DOMi was integrated into SeaMonkey 2.53 only in bug 1700003.
    • The full history is retained in our gitlab-master branch. The unofficial patch queue only includes the latest snapshot.
    • Initial clean-ups were done in bug 1701416.
    • DOMi has been dropped after 2.53. See bug 1273222.
  • The debugQA extension might be localized later.
  • WebExtension support in SeaMonkey is tracked in bug 1320556.
    • Work on theme or extension support has not started.
    • When we add WebExtension theme support lightweight theme support will be dropped. Full theme support will be kept at all costs because among other things our Modern theme depends on it.
    • Support for Webextension dictionaries and language packs has been added.
    • Manifest v3 support will be mandatory in the near future. Google no longer accepts new extensions using v2.
      • We do not plan to support this for now.
  • NoScript Classic 5.x is still available. Currently 5.1.9.
  • uBlock Origin is still available. The latest classic version is currently 1.16.4.30.
  • Session Manager is still being updated. Latest version is 0.8.1.14 and supports SeaMonkey 2.53.x.
  • Enigmail is supported again. Big thanks.
  • The Stylish forks stylem and stylem df version work in 2.53.13.
  • DownThemAll fixed 3.1.2 version for 2.53.10 and up.
  • Palefill generic polyfill can be used for accessing github, gitlab and other broken sites. Latest working version version is 1.23. Later versions are no longer working in SeaMonkey because of the developers decision to not fix some incompatible changes. Please disable updates or uninstall it.
  • github-wc-polyfill can be used for accessing github and gitlab. Both need Custom Elements support right now. Latest version is 1.2.19.
    • The add-on is outdated.
  • GreaseMonkey got broken by a needed locale code update in 2.53.15. See [1] for a do it yourself fix.
  • Sidebar for Facebook™ 52.0 gives Javascript error at startup, as follows:
[Exception... "Could not convert JavaScript argument arg 0 [nsISupports.QueryInterface]" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: jar:file:///~/.mozilla/seamonkey/xxxxxxxx.profilename/extensions/%7B11f349ad-067f-4254-8341-d7af23eecd99%7D.xpi!/bootstrap.js :: register :: line 533" data: no] 533

(home directory and profile name anonymized above). No bad effects on normal SeaMonkey working. Tonymec is going to disable this extension on his system. ✔ Done.

  • IanN created a SM version of the QuickText add-on.
  • The SeaMonkey and Thunderbird add-ons are now hosted on [2].
    • The old add-ons website api has been removed in bug 1402064 for Gecko 60 and up. We might need to do some further porting here to smoothly integrate installation from the add-ons site.
  • We will evalute the possibility of shipping pdf.js with SeaMonkey in a future release. frg will look into it when he finds some time.
  • Mozilla removed all classic add-ons from AMO. Rainer_Bielefeld filed bug 1517828 to see if missing add-ons can be re-added. The add-on converter also no longer works because of this.
    • Suggestion is to use a third party archive ca-archive and xpi.
  • NPAPI support including Flash has been fully removed in bug 1688415 and follow-ups.

2.Next

  • See Basics page for the usual reminders.
  • Sync is no longer working. The goal for 2.53 is to restore sync 1.1 and set up a sync 1.1 server.
    • Sync 1.1 has been removed from the mozilla source tree. If we want Sync 1.1 to work we need to fork it.
      • Pro: We control our own sync server and are not left at the mercies of Mozilla the next time they change their sync system.
      • Pro: Our users don't need an Fx Account.
      • Con: Can't sync with Firefox (unless someone writes a Sync 1.1 client for Firefox).
    • The sync ui has been disabled in 2.53+ in bug 1432273.
    • Long term we need someone to work on porting sync 1.5 over to replace legacy sync code after 2.57. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
      • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
      • bug 1003434 Add support for about:sync-progress.
      • Will probably never happen and we will stay at Sync 1.1
  • frg suggests doing an about:credits page for SeaMonkey contributors. This should link to a new list of people on the SeaMonkey project page.
    • IanN suggests about:smcredits.
    • The mozilla credits page still must be linked because there are many SeaMonkey contributors in it and Gecko is also still the foundation we did and are building on.
  • Tests are broken. Priority for new features or ports according to IanN is to get the code working.
    • frg suggests splitting off the tests to separate bugs for tracking and hopefully fixing in the future.
    • With the current dev resources at hand he is not very hopeful about fixing the tests anytime soon.
    • We test 2.53. by compiling the Thunderbird or Firefox code and use these tests.
  • We need to add Wayland support in the near future to 2.53.
  • Stalled Stuff. Needs a kick:
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • The project website is not localized. Only a basic German version is available which was created as a test some time ago. Support for other languages needs tool support and or integration with something like Poonton.
  • MDN stopped showing archived content on July 14th 2021. If bad links are found on the website and in SeaMonkey they will be updated as time permits.
  • Current breakages:
    • —

Feature List, Planning

Bug statistics for the last two (full) weeks: — new, — fixed, — triaged.

  • generally low activity on trunk, focus on branches towards releases

Open reviews/flags: 17 review 3 super-review 1 ui-review 24 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • Encrypted Media Extensions / Digital Rights Management
      • bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only
      • More work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox
  • Fundamental core features Firefox/Mozilla plans or did remove:
    • bug 1446341 The XUL "tree" widget will be removed from mozilla-central
      • Major bummer, will affect MailNews and other windows, Core bug 1446335
    • bug 1444685 XUL overlays are gone (SeaMonkey)
      • See Thunderbird bug 1444468, Core bug 1426763
      • Overlays were removed. Mozilla has converted tabbrowser.xml to tabbrowser.js. Needs to be done for SeaMonkey in a later release too.
    • bug 1222546 Product plan: remove support for heavyweight themes
      • This has been officially removed with Firefox 57. With Firefox 61 theme support has been removed from the source. The Modern theme no longer works in SeaMonkey.
    • bug 1397874 tracks the xbl bindings removal. xbl is gone and was replaced with custom elements and voodoo logic.
  • The website and wiki are outdated. InvisibleSmiley no longer maintains the website. The website was updated but it still needs work. Volunteers welcome.
  • frg suggested asking for donations in a future release. Probably during startup or more prominently on the website.
  • frg suggested a tabbrowser.xml overhaul because it's becoming harder to backport fixes from Firefox.
    • IanN suggests doing small patches which are easier to review.
  • There are reports that the PayPal donation on the website doesn't work for USD. It seems the amount is converted to Euro (probably correct if it is a German account).
  • Images should be vectorized and be svg if possible for future updates and HiDPI compatibility.
  • bug 1414390 needs to be ported. intl.locale.requested locale list needs to replace general.useragent.locale. Thunderbird did this in bug 1423532.
  • More and more websites do poor browser sniffing or pretend to require a later browser version.
    • We need to evaluate if a user agent switcher should be incorporated into SeaMonkey.
    • For some google services like maps you need to set a plain Firefox useragent to avoid problems.
  • bug 1463738 Bookmarks descriptions are taken out of Gecko 62.
  • Live bookmarks and rss support is taken out of Gecko 63 in bug 1477667. bug 1477670 might affect us too.
  • For updates the following bugs should be looked into:
    • bug 1274722 Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference.
    • bug 1271761 Add CPU features/detection to update URL.

Roundtable - Personal Status Updates

  • IanN generally will handle more complex review requests. frg, rsx11m, stefanh and ewong can also do reviews in their areas of expertise. For bigger changes and branch approvals outside of the build system IanN needs to be involved.
  • a+ from trusted regular patch authors/reviewers for ESR60 / 2.57 is implied as long as it only affects the suite directory. This will change back to a general needed a+ when the tree becomes more stable and will be announced then. If in doubt ask for approval.

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

ewong

frg

Didn't do that much in the last two weeks. Worked mostly on my wip js branch and did the 2.53.18.2 release. Rbeal life took unfortunately over again.

Waiting for review:

  • bug 1274798 Seamonkey integration in Gnome3. Old bug/patch which needs verification from someone more familiar with Linux.

Waiting for feedback:

  • bug 1410646 Fix SM "log into/onto" and related instances.

Checkin ready:

  • bug 1885748 SeaMonkey broken tab after undo closed tab with invalid protocol

Reviewing:

  • Patches from IanN

Working on:

  • Trying to get dynamic imports into 2.53.19. Halfway done but needs more code changes. While I hope to get it in in the next weeks no eta and no guarantees. Still missing prerequisites.
    • Working on a parallel branch to update SpiderMonkey for this and other stuff. 3/4 into 63a1 now and working.
      • Have import.meta now working there and starting with dynamic imports and bigint. Needs more backports. Support for allSettled redone with the original mozilla patches. Passes now more tests too.
  • Backporting bug 1634135 Enable new regexp engine. Waterfox Classic did it some time ago but our codebase is a bit different in parts here.
    • This took too long and preliminary patch from buc' is now in. This needs occasional rebasing but too much sites broke lately because of the missing regexp support.
  • bug 1296850 Show standard loading indicator images in tab when busy or progress attribute are set. Asked someone who wants to help out to look at the icons. Got the icons but have no time at the moment.
  • Bringing ICU and tzdata up to the current level for 2.53. Some progress with alignment of the intl code. Now at ICU 64.2.
  • RDF removal with IanN for 2.53 and up. Full removal for 2.53 will only happen if it does not break critical or too many add-ons.
  • bug 521861 After creating news account through clicking news URL Account Wizard is broken. jorgk found some issues in the patch which I need to fix first but buc came up with an alternate patch.
  • Port of bug 1100103 Add a remove button to every To/CC/BCC address in Composer. No bug yet. Initial version in 2.53. Needs better styling.

Not working on:

  • Fixing comm-central. Not worth it currently. Only see that it builds. With more backports we are slowly fixing central issues too.

Shelved for later:

  • Followups for bug 1379369 to TriggeringPrincipals and UserContextIDs in more functions. IanN already fixed a bunch of stuff.
  • bug 1370314 SeaMonkey 06/2017 installer rollup. Probably not much more right now. Took some parts to other bugs. and will see what is left when 2.57 is ready.

Titbits:

  • Separte wip branch of 2.53.19b1 pre now has Spidermonkey at about mid 63a1 level and progressing.

IanN

Mainly doing backports.

Checked in for website:

  • Nothing this time.

Checked in for 2.53.19+ / comm-central:

  • Nothing this time.

Waiting for checkin:

Waiting for review:

  • bug 1645892 Port changes to SSLStatus interfaces to SeaMonkey
  • bug 1646495 Stop using nsIDocShell::forcedCharset in SeaMonkey
  • bug 1687385 Update SeaMonkey mozconfigs
  • bug 1877001 Allow view-image to open a data: URI by setting a flag on the loadinfo
  • bug 1879726 Save-link-as feature should use the loading principal and context menu using nsIContentPolicy.TYPE_SAVE_AS_DOWNLOAD
  • bug 1885418 Update SeaMonkey website for 2.53.18.2 Final release

Waiting for feedback:

  • Nothing this time.

Working on:

  • bug 1633729 Update about:buildconfig to display comm as well as mozilla source information - comm-central part
  • bug 1616034 Update SessionStore code for SeaMonkey
  • bug 1612386 Don't always update lastRelatedTab information when browser.tabs.insertAllTabsAfterCurrent is true
  • bug 1577372 Working copy functionality was removed from page info window
  • bug 1573595 [meta]Update pageInfo files
  • bug 1578061 [meta]Update SeaMonkey's context menu
  • bug 1581176 [meta]Update SeaMonkey's certificate / net error handling UI
  • bug 1579640 Fix access key clashes in prefs
  • bug 657604 Remove the RDF global object. (Port bug 437869 to SeaMonkey.)
  • bug 1380613 sessionrestore will not restore anything if another tab is open
  • Backporting changes needed for build system

Back burner:

njsg

Rainer Bielefeld

Alternatives to the Mozilla SeaMonkey Wiki?

MediaWiki, DokuWiki, TWiki, Tiki Wiki and TiddlyWiki, as well as smaller players such as MoinMoin, PmWiki, PhpWiki and WikkaWiki?

rsx11m

Not really working on:

stefanh

Matt A. Tobin

tonymec

WG9s

Any other business?

  • We decided to switch the meeting schedule to a 3 week interval. If the date is a holiday it will be moved up a week and then goes back to 3 weeks.
    • Should business be booming again we will probably move back to the old schedule. For now not enough traffic to justify the two week schedule.
  • The next meeting will be held in three weeks on Sunday April 14th, 2024, 14:00 UTC (16:00 CET).
    • European Summer Time begins!
  • —
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2024-03-24&oldid=1250515"