SeaMonkey/StatusMeetings/2019-10-13

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:
    • WG9s Build Champion

Action Items

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

ANNOUNCEMENT

  • We moved our main irc presence to freenode. Please register your nick there and join us in the SeaMonkey freenode irc channel.
    • We will be on moznet irc too until it is turned off (planned for February 2020).

NEW

  • We have a new Sponsor. The announcement and website changes are done in bug 1588292.
  • —

OPEN

  • mozillaZine might close. Frank Lion set up a forum at SeaMonkey Board for SeaMonkey support issues and discussion.
    • IanN offered to take it over but has not heard back from the owner.
  • For future macOS releases we might need an Apple Developer ID and notarization process. See Notarizing Your App Before Distribution.
  • The project areas on the website need further updates to reflect the current responsibilities after some long time developers and maintainers left the project. bug 1356106 has already been filed.
  • Planning the future of SeaMonkey with a new infrastructure is in progress.
    • The documentation on the website needs to be updated for recent build config changes. frg can support anyone who wants to do this.
    • ewong started thinking about the servers needed for hosting releases and builds.
      • We are unsure how much traffic we need. WG9s might be able to help out initially with hosting builds.
    • IanN and frg do de-mozilla website changes in bug 1515507.
  • daniel mentioned that Azure Pipelines (build agent) is now free to use and also included free build time for Open Source projects.
    • ewong will look into it. It might be useful in the future to save us money. Currently we first set up Jenkins.
    • 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).

CLOSED

  • —

Status of the SeaMonkey Infrastructure

  • We are building up a new infrastructure using Azure.
    • Jenkins is being set up on the builders.
      • ewong is in the process of starting some jobs using Jenkins.
      • Also evaluation of Ansible and Terraform going together with it is done.
    • Cloning the mozilla- repos is problematic. They are huge and the process is slow.
      • Incremental updates need to be done whenever possible later.
    • ewong waits for info from mhoye to be able to work out traffic requirements.
  • Please see Infrastructure Status
  • frg thinks we should move the config files for building out of the source tree as much as possible.
    • IanN remarked that they are tied to the version in the tree.
    • 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.
  • We now have a presence on gitlab.
    • IanN is currently setting up a git repo for the 2.53.1 Beta 1.
    • Other repos for 2.57 and l10n will follow.
    • The repos will be made public after we tested building from them.
    • Patches will still be done via bugzilla first and then checked into hg.
    • Mozilla does this to a degree. See Mozilla gecko-dev repo as an example.
  • frg will update the Windows builder to VS2019 16.3 when we are sure that we do not need a 2.49.6 build.

Status of the SeaMonkey Source Tree

  • Starting with ESR60 2.57 all builds need to switch to mozilla as topsourcedir. Support for comm-central and comm-esr60 as top source dir is no longer supported.
    • Do not expect to use any 2.58+ release yet other than for checking if it builds. They are fundamentally broken by Mozilla source and api removals. We are currently fixing up 2.57 in the ESR60 repo right now and will tackle this later. Bugs for the 2.57 release will also land in comm-central.
  • [comm-central]:
    • Windows, macOS and Linux builds.
    • Do not use the comm-central release.
    • The installer still works...
    • l10n is broken in comm-central because of search plugin issues. If we switch to search/list.json then we need to keep the l10n searchplugin xml files for esr60 or switch esr60 too.
      • Fix for bug 1300198 will unbreak the comm-central l10n builds.
    • RDF has been completely removed now.
    • See bug 1452448 for current comm-central breakages. This is not up to date.
  • [comm-beta]:
    • We currently do not track nor update comm-beta.
    • Do not use any current comm-beta based release.
    • See bug 1452448 for current comm-central breakages.
  • [comm-release]:
    • We currently do not track nor update comm-release.
    • Do not use any current comm-release based release.
    • An updated unofficial 2.53 is available from WG9's website. We accept filing bugs against it. The next release will be based on 2.53 paving the way for 2.57.
    • See bug 1379370 for current 2.53 breakages. All known major bugs for 2.53 are closed.
    • For building please apply the patches from Bills website to the noted comm-release and mozilla-release changeset.
    • For building please stay at Rust 1.37 for now.
  • [comm-esr68]:
    • There are currently no plans for a SeaMonkey release based on comm-esr68.
    • Do not use any comm-esr68 based release.
    • We will not track nor update comm-esr68 for now
  • [comm-esr60]:
    • Sidebar, Help and Mail/News are broken because of XUL template removals. See bug 464710.
    • Do not expect to use the 2.57 release yet other than for testing.
    • An unofficial 2.57 is available from WG9's website. We accept filing bugs against it but it is only provided for testing purposes and not very usable at the moment.

Please file bugs only against the browser part or the ChatZilla and debugQA add-ons unless you know a specific problem is new and needs to be fixed. In any case check the existing bug reports to not generate bug noise.

    • If you want to use Rust 1.33 and up you need the patches available on Bills site.
    • Building with webrender enabled (unsupported and not working) with Rust 1.37 or higher currently does not work.
    • For building with stylo (default) please stay at Rust 1.37 for now.
    • See bug 1433370 for current 2.57 breakages.
  • [comm-esr52]:
    • See bug 1313304 for resolved issues.
    • SeaMonkey 2.49.5 has been released. We do not plan to release new versions from this repo.


Release Train

  • SeaMonkey 2.49.5 was released on September 4th
    • SeaMonkey 2.49.5 is likely the final minor release from comm-esr52, followed by 2.53.1.
    • The upcoming macOS 10.15 might cause problems with 2.49.5. bug 1556734 tracks known problems with Firefox. We advise users not to upgrade now. Fixes will be provided with the upcoming 2.53 version.
      • frg tested The official 2.49.5 with macOS 10.15 on his mac mini. It works fine for him but another user on irc reported an unspecified problem. Until the fog clears the update warning stays.
    • ewong uploadad crash symbols. Some seem to be missing.
    • IanN checks the crash stats and sees if he can identify or fix some of them.
    • Some minor release issues with the readme and checksums are looked into.
    • clang 8, gcc 7 and 8 are not usable for building 2.49.5 on Linux or for macOS.
      • Currently these versions produce a non working or "crashy" SeaMonkey.
      • clang 5 can be used instead of gcc 7 or 8.
      • gcc 4.8.5 was used to build the official 2.49.5 release.
      • According to distribution maintainers and users gcc 6.4, clang 6 and 7 also seem to work.
    • VS2017 is supported. VS2015 update 3 might work but is now unsupported.
    • The VS2017 toolset in VS2019 can be used too. Please ask frg for the patch.
    • The 2.49.5 release uses the following branches in hg:
  • SeaMonkey 2.53.1 / Gecko 56 in comm-release with unoffical patches.
    • 2.53.1 will be the next release after 2.49.5. Details are still being worked out.
  • The beta 1 release is tracked in bug 1584803.
    • Plan is to do at least frequent official beta releases in 2019.
    • A release would need l10n translations. The temporary solution for 2.57 will not work for this release.
    • The following bugs are not fixed in 2.53:
      • bug 1409458 "Privacy Issue: Replying to or forwarding an HTML e-mail with external content".
      • Building with the 10.11 SDK need the fixes in bug 1391790 for macOS 10.13.
    • Bill now hosts unofficial 2.53 l10n de builds on his wg9s de website.
    • A release would need further security fixes. frg tries to keep it as current as possible in his spare time.
      • The big security problems which were in the public up to 60.9 are fixed.
      • The current security level as of today is more or less at 60.4. Goal is to to be on par with latest ESR 60 soon.
      • ICU60, Skia m66, NSS 3.46.1, NSPR 4.22 and TLS 1.3 have been backported.
    • Compiler support is up to date
      • clang 7 or 8, gcc 5, gcc 6, gcc 7 and 8 can be used to build 2.53.1 on Linux or for macOS.
      • clang 7 or 8, VS2017 and VS2019 are supported under Windows. VS2015 is no longer supported.
      • clang 9 and gcc 9 support is being looked into.
    • Bill posts the patch files from frg containing the backported source and fixes on his wg9s website for 2.53.
      • frg maintains the patches for 2.53 on gitlab in a private repo. Anyone who wants access can send him an email but Bills repo is usually up to date.
      • Public official gitlab repos are currently being set up.
    • frg will do a preliminary 2.53 landing page for the website.
    • IanN will look into including My and pt-BR locales. frg can create patches based on l10n-release and l10n-central suite but these would need to be manually fixed by the translators and checked into a comm-release branch. We did this with nb-NO in bug 1391174.
    • WebExtentions dictionary support should be enabled as soon as possible in 2.53.
    • IanN reports that the internal devtools inspector works for chrome content in SeaMonkey. Please test and report your findings.
    • 2.53.1 has been updated extensively in the last 2 weeks. Please test the unofficial release and report any problems with it. All enhancements and fixes for the suite part go into 2.57 and up too.
  • SeaMonkey 2.57 Gecko 60 in comm-esr60.
    • SeaMonkey 2.57 will be developed together with 2.53 and then released as soon as possible.
      • Because of not enough developers this is a slow go and we will distribute 2.53 as an interim version.
    • 2.57 will be build from the comm-esr60 repo.
    • Mail and news are still broken in SeaMonkey 2.57 (Thunderbird is now at 60.9.0).
    • Thunderbird 68.1.1 is out but automatic updates will not be enabled for this release.
    • Not all patches with l10n-relevant string changes are done for 2.57. frg has figured out a way to do this using strings from later l10n-central releases (suite directory only). He tried this with a local l10n dir and it turned out ok.
      • IanN will test it later but there is currently no alternative presented.
      • IanN suggested asking Pike or flod about it.
      • With the preliminary solution no jenkins workarounds would be needed.
      • comm-central only patches must not delete any strings in the suite en-US directory until 2.57 is out.
      • When doing patches please make sure to change the l10n labels when the content changes.
      • cZ, DOMi, debugQA and the Lightning extension will be compatible with 2.57.
        • frg should have bug 1231349 fixed soon for 2.53 and 2.57 so the extensions will be included again.
    • Mail and news source structure has been aligned with Thunderbird in bug 1506440.
    • Thunderbird did switch to Web Extension dictionaries.
    • We will switch search plugins to a central json file for 2.57. See bug 1300198. TB and Fx did this long ago.
    • frg tries to back out the XUL template removals to make it faster usable again.
    • Compiling 2.57 with rust >= 1.33 needs fixes which are only in the unofficial patches queues. Webrender does not compile with rust 1.37 and up.
      • They can be put in a release branch later if mozilla does not fix this.
    • VS2019 16.1 is now able to build SeaMonkey 2.53 and 2.57.
      • frg did further private build fixes for 2.53 which will be used for 2.57 too.
    • The esr60 branch will be discontinued after 60.9.
      • We currently do not plan to switch to esr68 because of source plus api removals and changes. We will continue to use the esr60 branch for now.
  • General SeaMonkey release issues.
    • For now we will not use a Meta bug to track problems in ESER68. bug 1452448 for current comm-central breakages will kept up to date.
    • ewong tries to fix the update process for the aus3 server. This is broken since 2.48 and did not block the 2.49.4 release.
    • A meta bug for gtk3 compatibility has been created for 2.49.1 and up bug 1367257.
    • When updates are working again the following bugs need to be looked into:
      • bug 1274722 Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference.
      • bug 1271761 Add CPU features/detection to update URL.
    • 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.
  • Useful Firefox Release Schedule link: Releases Scheduling
    • Next Merge Day: October 21st (mozilla-beta → release: October 14th)
    • SeaMonkey is now at version 2.68a1. Gecko is at version 71, comm-esr68 (SeaMonkey 2.65) has been established.

Extensions and Plugins Compatibility Tracking

  • Most extensions are now broken in SeaMonkey 2.54+ because of Mozilla api removals.
    • WG9s fixed ChatZilla for 2.57. The patches have been reviewed and checked in.
      • It will probably never work again without a rewrite in 2.58+/61+ because of overlay and other removals.
    • DOMi is broken in 2.56+. See bug 1429936.
      • The developer of DOM Inspector Plus has fixed his extension and we can use the fixes for DOMi.
      • frg has DOMi working for 2.57 using the patches but some minor issues still remain.
        • A work-in-progress version is available at [1].
    • The devtools can inspect chrome content but this needs to be fixed in SeaMonkey. It works in Thunderbird.
      • DOMi might be retired later when this works. It is currently not built. See also bug 1273222.
    • The addon-SDK has been removed.
    • SMILE has been removed in 2.57.
    • Non bootstrapped add-on support has been removed in 2.58+.
    • Bootstrapped add-on support will be removed in Gecko 65.
    • Support for unpacked extensions has been removed.
    • Overlay support has been removed from Gecko 62. Thunderbird did build a lightweight solution for converting existing overlays.
    • Thunderbird has added preliminary WebExtension support to Thunderbird 63.
    • Lightning is packed directly into Thunderbird and SeaMonkey now. This was done in bug 1451847 for SeaMonkey.
      • While packed directly it is still maintained as an extension
    • Add-ons need to switch to optionsType 3 for 2.57. TB did a fix showing the preferences in the menu list. We need to port this bug for 2.57.
  • Thunderbird plans to discontinue classic add-ons with the next ESR78 based release.
    • Enigmail will be discontinued.
    • OpenPGP will be integrated. This is tracked in bug 22687.
    • Lightnig will be fully integrated by then.


  • cZ and DOMi should be integrated into SeaMonkey because of the l10n problem tracked in bug 1231349.
    • IanN suggested forking them and has created bug 1551033. The l10n files for DOMi will be moved into l10n-central.
      • IanN is ready to import them into the comm tree. He just needs to decide when and if (esp with DOMi if devtools can be got to work).
    • The language pack for cZ will be removed and a translated cZ will be included.
    • frg has regular l10n repack support almost finished for 2.53 and up.
  • WebExtension support in SeaMonkey is tracked in bug 1320556. As of now working on this has not started.
    • This would be needed for a ESR60 based SeaMonkey 2.57.
  • Evaluation if some extension functionality should be incorporated will need to be done for the 2.57 release.
    • Lightning is still working in 2.57 and directly distributed starting with 2.57.
    • NoScript, Adblock Plus and uBlock are broken in SeaMonkey 2.54+
    • SeaTab X2 and Version Number work in 2.57.
    • debugQA works in 2.57.
    • Chatzilla 0.9.94 works in 2.53 and 2.57.
  • NoScript Classic 5.x is still being updated. You can get it from [2]. Currently 5.1.9.
  • uBlock Origin is still being updated. You can get it from [3]. You need to pick the latest legacy version. Currently 1.16.4.11.
  • The SeaMonkey and Thunderbird add-ons are now hosted on [4].
    • [5] redirects to it. 2.57 has already been switched over to the new site in bug 1475799.
      • 2.57, comm-central and the inofficial 2.53 already have updated prefs. We plan to do this for a future 2.49 release.
    • 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.

    • For Thunderbird a new add-on [6] is available to switch addons.mozilla.org to addons.thunderbird net.
    • The website has been updated and points to [7].
  • 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.

2.x (Last, Current, Next)

  • See Basics page for the usual reminders.
  • Old add-on signing methods have been removed. SeaMonkey and Thunderbird still use them per thread "removing "the old way" of signing add-ons" in mozilla.dev.platform. Apparently xpinstallConfirm.xul contained the references to them.


2.49.x current releases (done)

open tracking (0) tracking requests (1) targeted (0) fixed (92)

2.53.x next release branch (in progress)

open tracking (1) tracking requests (17) targeted (0) fixed (29)

2.57.x next esr release branch (future)

open tracking (0) tracking requests (2) targeted (0) fixed (177)

2.Next

  • Sync is no longer working. The goal for 2.53 and 2.57 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.57+ 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.
  • 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.

  • The search.json format will change soon. We need to look into this only if we plan to do a ESR 76 based release.
  • We might need new SeaMonkey bugzilla component for tracking website problems with our product.
    • 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.
      • 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 probles with specific websites only should be disucssed in the support groups first.
  • Stalled. Needs a kick:
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • —
  • Mozilla-central bugs that affect us:
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
  • [rsx11m] did open bug bug 1305902 for certificate pinning. Discussion if it should be enabled for SeaMonkey is still underway. Callek commented in the bug.

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: 20 review 3 super-review 1 ui-review 9 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)
    • 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. Only bindings used in Firefox will be kept for now until they are replaced with who-knows-what.
      • Overlays are now also gradually being removed. Mozilla has converted tabbrowser.xml to tabbrowser.js. Needs to be done for SeaMonkey in a later release too.
  • 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 servicves like maps you need to set a plain Firefox useragent to avoid problems.
    • For github you need to set the gecko Version to 60.
    • We plan to add a generic user agent for github and 2.49 / 2.53 only. See bug 1505460.
  • 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.

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

Most work for SeaMonkey in the last two weeks was again fixing up 2.53 for a Beta 1 release and doing support.

Waiting for review:

  • bug 1274798 Seamonkey integration in Gnome3. Old bug/patch which needs verification from someone more familiar with Linux.
  • bug 1588358 Clean up SeaMonkey migration code.

Waiting for esr60 a+:

  • Nothing

Waiting for feedback:

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

Checkin ready:

  • Again several bugs from IanN. Will be done today.

Reviewing:

  • bug 1536779 Port |Bug 1528840 - addressingWidgetOverlay.js, abMailListDialog.js code cleanup| to SeaMonkey. Postponed till 2.57 is in better shape.
  • A bunch of patches from IanN.

Working on:

  • Making sure SeaMonkey 2.53 and up will work on macOS 10.15.
  • bug 1231349 l10n repacks broken on with SM 2.42 and newer. cZ patch done for 2.57 and up. Got feedback but found a bug yesterday. Backport to 2.53 later.
  • bug 1231349 l10n repacks broken on with SM 2.42 and newer. DOMi patch mostly working. cZ got f+. Shooting for r+ next.
  • Doing local 2.53 l10n builds to assess how much would be missing for a possible release.
  • Fixing up mailnews for 2.57. Starting to see if I can back out the xul templates removal to speed things up. Second bug backed out but still no luck.
  • Backporting ESR 60 fixes to 2.53. At 60.3 now. Much progress with bringing Lighting up to date. Everything relevant up to 60.9 in and now a packed extension.
  • 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.
  • Integrating DOMi Plus patches into DOMi.
  • 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.
    • 2.58+ is broken in capital letters as in BROKEN.

Shelved for later:

  • 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.
  • bug 1379062 Enable cross-compile on SeaMonkey Linux machines. 2.49.x to 2.57 compiles fine locally.
  • bug 1392929 Port Bug 886907 [Remove old synchronous contentPrefService] to SeaMonkey.
  • Followups for bug 1379369 to TriggeringPrincipals and UserContextIDs in more functions.
  • 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.
  • Helping MMR with bug 1444740 Drop support for -moz-border-*-colors in SeaMonkey. He seems to have dropped out :(

Titbits:

  • Busy with SeaMonkey work and real life.

IanN

Fixed for SM (2.53+):

  • bug 1576618 Port |bug 1330467 - Add SitePermissions APIs functions to accept principal and use them| to SeaMonkey
  • bug 1576614 Port |bug 1452361 - Don't reset to default permissions for cookies in page info| to SeaMonkey
  • bug 1579735 Let PB windows be identified by backend and themes
  • bug 1578067 Update openLinkIn() and use more
  • bug 1581177 Port {{|Bug|989197}} - Use URLSearchParams instead of regex to parse params in about:net/certerror URLs| to SeaMonkey
  • bug 1584827 Port some changes to search bar bindings to SeaMonkey

Waiting for check-in:

Waiting for review:

  • bug 1536779 Port |bug 1528840 - addressingWidgetOverlay.js, abMailListDialog.js code cleanup| to SeaMonkey
  • bug 1580348 Port |bug 906190 - Persist "disable protection" option for Mixed Content Blocker in child tabs| to SeaMonkey
  • bug 1580697 Fix servo/webrender code in SM2.53 for rustc 1.37
  • bug 1581314 Introduce a framework for expanding certerror code to handle neterrors
  • bug 1581508 Improve RSS feed display in SeaMonkey

Working on:

Back burner:

Rainer Bielefeld

rsx11m

Looking into:

  • bug 1441016 Port bug 1414390 "Add intl.locale.requested locale list to replace general.useragent.locale" to SeaMonkey

Not really working on:

  • bug 1437393 Font lists in preferences are no longer grouped by font type, port asynchronous handling like bug 1399206
  • bug 1318852 Make labels of cmd_properties action-oriented and context-sensitive, e.g. "Edit Contact", "Edit List", etc.
    • "real" fix

stefanh

tonymec

Any other business?

  • The next meeting will be held in two weeks on Sunday October 27, 2019, 14:00 UTC (16:00 CET), on the regular meeting schedule.
    • this is the end of European Summer Time thus please watch the announcement! (15:00 CET)
  • WG9s proposed to make each Sunday 14:00 UTC (15/16:00 CET) a general meeting time. If no status meeting is scheduled at this day whoever is available can tune in for an ad-hoc meeting.
  • —
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2019-10-13&oldid=1218960"