MozillaWiki - Recent changes [en]

Firefox/Channels/Meetings/2026-11-05

Dmeehan — Thu, 05 Nov 2026 15:37:52 GMT

Created page with " <center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | index | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center> '''Channel Meeting Details'..."

New page

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Thursdays at 7:30am Pacific Time
* Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings

'''Video/Teleconference Details'''
* Zoom Meeting ID: 536 097 768
* https://mozilla.zoom.us/j/536097768

{{Notes}}

__FORCETOC__

== Attendees ==
dmeehan, ljanos, dsmith, oardelean, RyanVM, dbarladeanu, gasofie, Aryx,jgibbs, btot, dveditz

== Schedule Update ==
* 159
** Desktop 159.0.1 and Android Fenix/Focus 159.0.1 planned release live @ 100% rollout
** No dot release on the radar before Fx160 go-live
* 160
** Desktop & Android 160.0b5 live on beta @ 100% rollout
** Desktop & Android 160 RC1 ready for QA
*** Will start Android Fenix/Focus 160.0 5% Play Store rollout later today
** ESR 115.45 and 153.7 are pending release
** iOS Firefox 160.0 scheduled to start phased rollout at 03:00 UTC on 2026-11-08
** Firefox iOS 160.1 branches and Firefox iOS 160.1 gtb tomorrow
** Next week is Fx160 go-live on 2026-11-10
* 161
** Merge Day and 161.0b1 build1 gtb today
*** We have infra problems (bug 2089531), gtb might be delayed to tomorrow
** 161.0b1 goes live @ 50% on 2026-11-09

== Release Quality Metrics ==
* https://bugdash.moz.tools/#tab.beta

== Desktop Stability ==
=== Nightly ===
crash incidence (% of users experiencing a crash): 1.82% (+0.08pp compared to previous week)

=== Beta ===
crash incidence: 1.85% on Nov 1 (-0.32pp)

=== Release ===
crash incidence: 1.06% (+/-0pp)

== Mobile Stability ==
=== Release ===
* Crash in [@ mozilla::dom::syncedcontext::Transaction<T>::Commit | mozilla::dom::BrowsingContext::SetOpenerPolicy]
** https://bugzilla.mozilla.org/show_bug.cgi?id=1981758
** pending triage
* Crash in [@ java.lang.OutOfMemoryError: at android.os.Message.obtain(Message.java)]
** https://bugzilla.mozilla.org/show_bug.cgi?id=2089609
** crash volume increased steadily
** triage owner needinfoed

== QA ==
=== Nightly ===
* New feature testing
** Nightly 161 new features - test case design and documentation - in progress
=== Aurora / Dev Edition ===
=== Beta ===
* Uplift verification for Beta 160 features will start next week

=== Mobile ===
[ljanos]
* Android
** Build Signoffs Fenix & Focus
*** Beta 161.0b3- sign-off status GREEN
*** Beta 161.0b4 - sign-off status GREEN
*** Beta 161.0b5 - sign-off status GREEN
*** RC 159.0.1 - sign-off status GREEN
*** RC 160.0 - sign-off status GREEN

** Feature Testing
*** [QA -5999] Android - REdownloads tracking - Nightly 161 (Green)
*** [QA - 5898] PDF Signatures - Nightly 161 – in progress
*** [QA-5899] Collections to Tab Groups migration - Beta 160 - in progress
*** [QA-5817] [Android] - Android - Listen to Page - Nightly 161 (Green)
*** [QA-4205] [Android] - Homepage as a New Tab - Nightly 161 (Yellow)
*** [QA-5922] Android: Weekly Privacy Report Notifications - Beta 160 (Yellow)

* iOS
** Build Signoffs
*** Firefox iOS 160.0 (79537) - Release Candidate 1- status [GREEN]
*** Focus iOS 160.0 (79546) - Release Candidate 1- status [GREEN]

** Feature Testing
*** [QA-5964] - Quick Answers phase 2 - New opt-in redesign - nightly testing in progress
*** [QA-6023] - Quick Answers phase 3 - Follow up - nightly testing in progress

== Action items ==

== Roundtable & Special Topics ==
* 2026-11-11 is a public holiday in several regions

[[category:Channel_Meetings|{{SUBPAGENAME}}]]
[[Category:Wikipage templates]]

Template:Version/Thunderbird/release/current

SpikeUK1 — Thu, 05 Nov 2026 15:17:21 GMT

Update Thunderbird version to 159.0

← Older revision		Revision as of 15:17, 5 November 2026
Line 1:		Line 1:
	~~158~~.0		159.0

Template:THUNDERBIRD RELEASE DATE

SpikeUK1 — Thu, 05 Nov 2026 15:16:07 GMT

Add Thunderbird version 159.0 = 2026-10-27

← Older revision		Revision as of 15:16, 5 November 2026
Line 393:		Line 393:
	\| 157.0.1 = 2026-10-01		\| 157.0.1 = 2026-10-01
	\| 158.0 = 2026-10-13		\| 158.0 = 2026-10-13
			\| 159.0 = 2026-10-27
	\| some date in the past		\| some date in the past
	}}		}}
	<!-- "some date in the past" should remain here. It is used to check if all the data are present -->		<!-- "some date in the past" should remain here. It is used to check if all the data are present -->

Template:Version/Firefox/release/current

SpikeUK1 — Thu, 05 Nov 2026 15:08:59 GMT

Update Firefox version from 159.0 to 159.0.1

← Older revision		Revision as of 15:08, 5 November 2026
Line 1:		Line 1:
	159.0		159.0.1

Template:FIREFOX RELEASE DATE

SpikeUK1 — Thu, 05 Nov 2026 15:08:16 GMT

Add Firefox version 159.0.1 = 2026-11-03

← Older revision		Revision as of 15:08, 5 November 2026
Line 564:		Line 564:
	\| 158.0 = 2026-10-13		\| 158.0 = 2026-10-13
	\| 159.0 = 2026-10-27		\| 159.0 = 2026-10-27
			\| 159.0.1 = 2026-11-03
	\| 160.0 = 2026-11-10		\| 160.0 = 2026-11-10
	\| 161.0 = 2026-11-24		\| 161.0 = 2026-11-24

User:SpikeUK1

SpikeUK1 — Thu, 05 Nov 2026 14:56:52 GMT

Account approvals : November 2026: Nine likely spammer/s rejected. Backlog zero.

← Older revision		Revision as of 14:56, 5 November 2026
Line 248:		Line 248:
	\|-		\|-
	\| 4<sup>th</sup> November 2026 \|\| 0 \|\| 2 \|\| 0 \|\| 0 \|\| 2		\| 4<sup>th</sup> November 2026 \|\| 0 \|\| 2 \|\| 0 \|\| 0 \|\| 2
			\|-
			\| 5<sup>th</sup> November 2026 \|\| 0 \|\| 9 \|\| 0 \|\| 0 \|\| 9
	\|}		\|}

Template:NextReleaseDate

Pascalc — Thu, 05 Nov 2026 12:11:57 GMT

160

← Older revision		Revision as of 12:11, 5 November 2026
Line 1:		Line 1:
	2026-10~~-27~~		2026-11-10

Template:Version/Gecko/release/current

Pascalc — Thu, 05 Nov 2026 12:11:11 GMT

160

← Older revision		Revision as of 12:11, 5 November 2026
Line 1:		Line 1:
	~~159~~		160

Template:Version/Gecko/beta/current

Pascalc — Thu, 05 Nov 2026 12:11:00 GMT

161

← Older revision		Revision as of 12:11, 5 November 2026
Line 1:		Line 1:
	~~160~~		161

Template:Version/Gecko/central/current

Pascalc — Thu, 05 Nov 2026 12:10:46 GMT

162

← Older revision		Revision as of 12:10, 5 November 2026
Line 1:		Line 1:
	~~161~~		162

Template:Version/Gecko/release/next

Pascalc — Thu, 05 Nov 2026 12:10:33 GMT

161

← Older revision		Revision as of 12:10, 5 November 2026
Line 1:		Line 1:
	~~160~~		161

CA/Netlock Issues

Bwilson — Thu, 05 Nov 2026 04:53:22 GMT

A.2. Renewed concerns and corrective commitments in 2024–2025: Minor edit

@@ Line 24: / Line 24: @@
 === A.2. Renewed concerns and corrective commitments in 2024–2025 ===
-In [https://bugzilla.mozilla.org/show_bug.cgi?id=1904041#c8 Bug 1904041, Comment 8], Chrome's Ryan Dickson criticized Netlock's incident handling and asked why it had regressed after similar concerns approximately thirteen months earlier.
+In [https://bugzilla.mozilla.org/show_bug.cgi?id=1904041#c8 Bug 1904041, Comment 8], Chrome criticized Netlock's incident handling and asked why it had regressed after similar concerns approximately thirteen months earlier.
 Mozilla subsequently opened [https://bugzilla.mozilla.org/show_bug.cgi?id=1957474 Bug 1957474] over missing weekly updates in four incidents: Bugs 1904041, 1905509, 1947691 and 1917046. Even the report about missing updates required reminders about preliminary and full reporting obligations. Netlock ultimately reported implementing ticketing reminders, compliance-calendar integration, a designated coordinator, automated alerts, and clearer accountability. The incident was closed in June 2025 after Netlock reported completion of its action items.
@@ Line 191: / Line 191: @@
 * Bugs 1891331 and 1947691 represent the same delayed-revocation episode. Bugs 1905509 and 1906115 contain related material about the same 2024 reporting-contact problem.
 * Root inclusion requests and routine root transitions are not themselves evidence of non-compliance. No assertion of current audit delinquency is made here without the relevant audit records and deadlines being verified.

CA/Netlock Issues

Bwilson — Wed, 04 Nov 2026 23:31:22 GMT

Initial post

New page

{{draft}}
'''This near-final draft remains subject to verification and amendment, including checks of citations, quotations, cross-references, incident status, and the characterization of related or superseded reports. Technical findings and remediation claims attributed to others have not necessarily been independently verified. Mozilla has not yet determined the timing, scope, or manner of trust removal.'''

= Netlock Issues =

This page summarizes publicly documented issues involving NETLOCK Kft. (Netlock), including recurring deficiencies in incident response, certificate revocation, certificate issuance, disclosure, and revocation services. It is not necessarily comprehensive and may be updated by Mozilla as additional information becomes available. Please do not edit this page directly. Proposed corrections or additions should be sent to the Mozilla dev-security-policy discussion list or to certificates@mozilla.org.

The issues are grouped by subject rather than presented strictly chronologically. Closed incidents remain relevant to understanding Netlock's commitments and subsequent performance. Related reports concerning the same event are identified together.

== Summary ==

The central concern is Netlock's ability to sustain effective controls across its publicly trusted CA operations. The public record includes repeated failures to provide timely incident updates, respond to certificate problem reports, revoke non-compliant certificates, and identify the full scope of technical defects. Several later reports expressly acknowledge recurrence after earlier corrective measures had been reported complete.

Individual fixes and improvements are acknowledged below. The cumulative assessment concerns whether those measures have produced reliable, continuing compliance and effective public accountability.

== Issue A: Repeated failures to maintain incident updates and answer questions (2018–2026) ==

=== A.1. Prolonged silence in an early misissuance incident ===

In [https://bugzilla.mozilla.org/show_bug.cgi?id=1462423 Bug 1462423], involving seven precertificates whose common names were not represented in their subject alternative names, Ryan Sleevi noted in Comment 2 that approximately eight months had passed without an update or response. Netlock later explained that it had acted on the direct report but missed Bugzilla notifications. The distinction matters: technical remediation did not discharge the separate obligation to report publicly and respond to questions.

Mozilla opened [https://bugzilla.mozilla.org/show_bug.cgi?id=1572992 Bug 1572992] in 2019 because of repeated failures to respond and update that incident. Netlock attributed missed responses to mail filtering and misunderstanding comments. It reported whitelisting Bugzilla mail, changing its handling of unclear requests, and transferring contact duties to a dedicated team. The bug was subsequently resolved FIXED.

=== A.2. Renewed concerns and corrective commitments in 2024–2025 ===

In [https://bugzilla.mozilla.org/show_bug.cgi?id=1904041#c8 Bug 1904041, Comment 8], Chrome's Ryan Dickson criticized Netlock's incident handling and asked why it had regressed after similar concerns approximately thirteen months earlier.

Mozilla subsequently opened [https://bugzilla.mozilla.org/show_bug.cgi?id=1957474 Bug 1957474] over missing weekly updates in four incidents: Bugs 1904041, 1905509, 1947691 and 1917046. Even the report about missing updates required reminders about preliminary and full reporting obligations. Netlock ultimately reported implementing ticketing reminders, compliance-calendar integration, a designated coordinator, automated alerts, and clearer accountability. The incident was closed in June 2025 after Netlock reported completion of its action items.

=== A.3. Further recurrence in 2026 ===

In [https://bugzilla.mozilla.org/show_bug.cgi?id=2052541#c15 Bug 2052541, Comment 15], Netlock documented gaps between its own posts of 49 days in that bug, 45 days in Bug 2004699, and 39 days in each of Bugs 2051459 and 2063842. Four committed action dates passed without reporting. Netlock acknowledged that this repeated earlier failures and had not yet fully established why its 2025 controls failed.

[https://bugzilla.mozilla.org/show_bug.cgi?id=2052541#c16 Comment 16] disclosed failure of the first cycle of its new update control: reminders fired but went to people other than the responsible owner and deputy. Netlock reported correcting and testing the routing on 9 October 2026.

Further missed updates and report commitments were recorded in [https://bugzilla.mozilla.org/show_bug.cgi?id=2004699#c50 Bug 2004699, Comments 50–51], [https://bugzilla.mozilla.org/show_bug.cgi?id=2063842#c4 Bug 2063842, Comment 4], and [https://bugzilla.mozilla.org/show_bug.cgi?id=2075720#c1 Bug 2075720, Comment 1]. These are documented recurrences, rather than conclusions drawn solely from the age of an open bug.

Issues: Incident response; public accountability; organizational continuity; ineffective corrective actions.

== Issue B: Certificate problem reports were not handled within the required timeframe (2024 and 2026) ==

[https://bugzilla.mozilla.org/show_bug.cgi?id=1905509 Bug 1905509] documents failure to respond within 24 hours to a 2024 certificate problem report sent to the contact published in Netlock's CP/CPS. Staff treated that address as a channel for policy questions rather than recognizing the certificate problem report. Published contact information also differed between the CP/CPS and CCADB. The related [https://bugzilla.mozilla.org/show_bug.cgi?id=1906115 Bug 1906115] addresses the published reporting instructions.

Netlock reported creating a dedicated reporting address, updating its documentation, training staff, and establishing notifications to several departments.

Nevertheless, [https://bugzilla.mozilla.org/show_bug.cgi?id=2052541 Bug 2052541] records another failure in June 2026: reports were diverted to spam or not escalated from secondary channels. The first substantive reply arrived about sixteen days after the initial report and asked which certificate was affected.

Issues: Problem-report intake; escalation; monitoring; recurrence after remediation.

== Issue C: Repeated failures to disclose incidents on time and prepare adequate reports (2025–2026) ==

[https://bugzilla.mozilla.org/show_bug.cgi?id=2007948 Bug 2007948] records failure to publish a full incident report within the required fourteen-day period in connection with the AIA encoding incident. Its discussion also questioned whether earlier multi-person review commitments provided effective technical verification.

[https://bugzilla.mozilla.org/show_bug.cgi?id=2013400 Bug 2013400] records a separate failure to make the initial disclosure within 72 hours after receiving a report on 12 January 2026. Netlock acknowledged that its tracking used the Bugzilla filing date rather than first awareness, misaligning its reporting deadlines. It committed to awareness-based tracking and automated countdown alerts.

That control did not prevent the subsequent failure in [https://bugzilla.mozilla.org/show_bug.cgi?id=2063842 Bug 2063842]. Netlock became aware of the OCSP incident on 16 June 2026 but did not publish its report until 3 July. It later explained that the countdown control covered externally filed tickets but did not start for internally detected incidents. Technical correction on 17 June had been treated as an operational fix without triggering public incident disclosure.

[https://bugzilla.mozilla.org/show_bug.cgi?id=2013395 Bug 2013395] concerns an unduly narrow interpretation of the related-incidents requirement: Netlock considered its own incidents rather than relevant incidents across the ecosystem. This reduced the opportunity to learn from comparable failures elsewhere.

The October 2026 reports in [https://bugzilla.mozilla.org/show_bug.cgi?id=2075255#c6 Bug 2075255], [https://bugzilla.mozilla.org/show_bug.cgi?id=2075258#c5 Bug 2075258], and [https://bugzilla.mozilla.org/show_bug.cgi?id=2075720#c2 Bug 2075720] again acknowledged late full reports. Revised dates did not make the original reporting deadlines cease to apply.

Issues: Late disclosure; report completeness; deadline calculation; learning from other CAs.

== Issue D: Repeated delayed revocation and subscriber-dependent compliance decisions (2020–2025) ==

In [https://bugzilla.mozilla.org/show_bug.cgi?id=1688844 Bug 1688844], related to the certificate-profile issue in [https://bugzilla.mozilla.org/show_bug.cgi?id=1680378 Bug 1680378], Netlock identified the problem on 20 November 2020 but did not revoke the final affected certificate until 31 December. Netlock subsequently committed to clarifying internal revocation procedures and recognizing no exception to the applicable 24-hour or five-day deadlines.

In [https://bugzilla.mozilla.org/show_bug.cgi?id=1822809 Bug 1822809], Netlock again delayed revocation of non-compliant certificates, this time those containing prohibited organizationalUnitName fields. Its initial account explicitly attributed the delay to a business decision to accommodate customer requests, despite the five-day requirement.

The same decision pattern appeared in the 2024 policy-qualifier incident. [https://bugzilla.mozilla.org/show_bug.cgi?id=1891331 Bug 1891331], subsequently superseded by [https://bugzilla.mozilla.org/show_bug.cgi?id=1947691 Bug 1947691], documented extending revocation for subscribers described as important to the national economy. The latter report states that delayed revocations were completed on 30 April 2024.

Mozilla rejected subscriber importance and operational inconvenience as exceptions. Netlock later acknowledged that its policies, subscriber contracts, escalation arrangements, and revocation preparedness had been insufficient. Its closure material reported revised contracts, readiness reviews, escalation procedures, and a mass-revocation simulation. Those reported improvements are relevant, but the repeated earlier decisions demonstrate that the problem extended beyond a single certificate-profile defect.

Issues: Delayed revocation; compliance governance; subscriber readiness; emergency response.

== Issue E: Certificate-profile changes and issuance checks did not reliably prevent misissuance (2018–2026) ==

The record includes multiple failures to apply requirements consistently across issuance paths:

* [https://bugzilla.mozilla.org/show_bug.cgi?id=1462423 Bug 1462423]: seven precertificates issued in May 2018 had common names absent from their DNS SANs. A production configuration placeholder and differences between precertificates and final certificates were discussed in the report.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1676367 Bug 1676367]: precertificates exceeding 398 days were issued after the September 2020 limit took effect. Netlock explained that testing covered new orders but omitted orders already in progress. It subsequently applied the same checks to precertificates and ordinary certificates.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1820174 Bug 1820174]: TLS certificates continued to include organizationalUnitName after its prohibition. Netlock reported changing its software, request forms and policies. A later update described weekly manual linting while automated checking remained under investigation.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1889570 Bug 1889570]: prohibited user-notice policy qualifiers remained in TLS certificate profiles after the September 2023 requirements change. Netlock reported that its profile review had missed the change.

These incidents show gaps in requirements tracking, coverage of production paths, and verification before issuance. Completing a profile correction does not by itself establish that every path using the same configuration or workflow has been checked.

Issues: Requirements implementation; testing coverage; linting; precertificate controls.

== Issue F: CCADB disclosures were incomplete, incorrect, or insufficiently verified (2024–2026) ==

=== F.1. Four intermediate certificates were not disclosed on time ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=1904041 Bug 1904041] documents four intermediate CA certificates not disclosed within the required period. Netlock initially asserted that disclosure had been completed, but had entered different certificates with the same subject names and public keys under a root not yet trusted by participating programs.

Rob Stradling repeatedly explained the distinction. Netlock's later timeline places confirmation of the problem on 19 June 2024 and correct disclosure on 18 July. Netlock acknowledged insufficient experience and process controls. It reported a disclosure checklist, checker tool and additional training.

The earlier allegation concerning an additional fifth certificate was withdrawn in Comment 6 because that certificate did not chain to a trusted root. It is not included here as a separate violation.

=== F.2. CRL URL disclosure failures recurred ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=2001327 Bug 2001327] concerns missing CRL distribution-point disclosures. Netlock expanded the affected set to four unused CA certificates, reported revoking them in December 2025, and introduced recurring weekly disclosure checks.

In [https://bugzilla.mozilla.org/show_bug.cgi?id=2075258#c5 Bug 2075258, Comment 5], Netlock expressly acknowledged recurrence. CCADB contained a CRL URL variant on one host while certificates used different URLs across three hosts. The earlier weekly check had not caught the discrepancy. Its October report also acknowledged missing its own 29 September correction date; a disclosed RQSCD CRL URL returned HTTP 404 during its checks.

This discrepancy affected oversight as well as metadata accuracy: monitors using CCADB could retrieve a different CRL from the one used by relying parties following certificate distribution points.

Issues: Disclosure accuracy; verification; certificate identity; ineffective monitoring.

== Issue G: Revocation information was stale, incorrectly encoded, inconsistent, or incomplete (2023–2026) ==

=== G.1. Earlier CRL and revocation-reason failures ===

In [https://bugzilla.mozilla.org/show_bug.cgi?id=1819105 Bug 1819105], the disclosed CRL for NETLOCK Trust EV CA 3 had a nextUpdate in 2020 when reported in 2023. Netlock explained that the CA was used for test certificates and monitored at the infrastructure level rather than with sufficient checks of the published CRL.

[https://bugzilla.mozilla.org/show_bug.cgi?id=1830823 Bug 1830823] records use of certificateHold for precertificates. The issue was identified during a different discussion, and a community member opened the separate incident after Netlock had not done so.

[https://bugzilla.mozilla.org/show_bug.cgi?id=1938167 Bug 1938167] records CRLs served in PEM rather than DER encoding. Netlock reported correcting the files, changing publication validation, and integrating linting. The closure account explicitly identified a lack of encoding enforcement in CRL and AIA publication processes.

=== G.2. A previously remediated reason-code defect persisted across other paths ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=2011314 Bug 2011314] concerned an explicit unspecified (0) reasonCode in a CRL. Netlock reported remediation and verification before closure in June 2026.

Nevertheless, [https://bugzilla.mozilla.org/show_bug.cgi?id=2075255#c6 Bug 2075255, Comment 6] acknowledged recurrence across several CAs. Automatic revocation after a suspension period still wrote explicit reasonCode 0. Netlock's 14 October update stated that the fix had passed tests but was not yet deployed. The incident illustrates incomplete coverage of a shared workflow rather than merely retention of historical entries.

=== G.3. Different CRL contents were published under the same number ===

The full report in [https://bugzilla.mozilla.org/show_bug.cgi?id=2075720#c2 Bug 2075720, Comment 2] states that 13 of 16 CRLs in the Gold hierarchy had different contents under the same cRLNumber across two URL variants in its 9 October 2026 measurement. The variants did not contain an Issuing Distribution Point distinguishing their scopes. Another CRL lacked cRLNumber entirely.

The root CRL was also reported to change at a single URL without an increased number or updated issuance time. Netlock acknowledged that its monitoring did not compare the variants. Its report said the observed differences concerned expired certificates in the cases examined, while verification of that conclusion across the entire population remained an action item.

Issues: Revocation-data integrity; scope assessment; monitoring; incomplete remediation.

== Issue H: Publication and status-service checks did not verify the required behavior (2025–2026) ==

=== H.1. AIA encoding failures survived earlier publication improvements ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=2004699 Bug 2004699] records issuer certificates served in PEM rather than DER from AIA HTTP endpoints. Later investigation broadened the affected endpoint population and identified a regression.

In [https://bugzilla.mozilla.org/show_bug.cgi?id=2004699#c49 Comment 49], Netlock reported successful external verification of the encoding fix on 2 October 2026. It subsequently reported that the fix continued to hold. However, Comments 50–51 recorded missed commitments to provide the updated full report, explain the regression, and reconcile the published AIA inventory against internal issuance records. The operational correction and the unfinished investigation should be assessed separately.

=== H.2. OCSP did not recognize an issued certificate ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=2051459 Bug 2051459] records an issued certificate not propagated to the OCSP responder. The responder returned unknown for approximately eleven days in June 2026. Netlock identified missing synchronization verification and dedicated monitoring, later acknowledged the detection delay, and reported a subsequent reconciliation of its valid TLS certificate inventory against responder status.

=== H.3. Test sites did not present the required certificate states ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=1962426 Bug 1962426] records a designated valid test site serving an expired certificate in April 2025. [https://bugzilla.mozilla.org/show_bug.cgi?id=1979287 Bug 1979287] records a July 2025 finding that the revoked test site instead served an expired certificate; Netlock described a manual maintenance process that omitted the revocation step. These are further examples of checks failing to verify the intended externally visible state.

=== H.4. Policy-document repository availability ===

[https://bugzilla.mozilla.org/show_bug.cgi?id=2021559 Bug 2021559] records a March 2026 document-repository outage. Netlock attributed it to excessive requests, database-connection exhaustion, and corruption of supporting tables. General website monitoring did not specifically check document downloadability. Its closure material reported restoration, targeted monitoring, and architectural improvements. This incident was internally detected and should not be characterized as exclusively dependent on external reporting.

Issues: End-to-end verification; inventory reconciliation; service monitoring; operational resilience.

== Issue I: Audit findings and audit-document identification weaknesses (2021–2024) ==

[https://bugzilla.mozilla.org/show_bug.cgi?id=1716874 Bug 1716874] concerns an intermediate CA apparently missing from audit reports. Netlock explained that the report contained an incorrect SHA-256 fingerprint, requiring clarification of the certificate's identification. This should not be described as a proven unaudited period without examining the corrected evidence.

[https://bugzilla.mozilla.org/show_bug.cgi?id=1917046 Bug 1917046] records four groups of findings in Netlock's 2024 audit: incomplete asset inventories; missing information in backup-restoration test records; crisis-management documentation and testing deficiencies; and supply-chain evaluation that omitted cybersecurity requirements. Netlock later reported completing the corrective actions, and the bug was resolved FIXED.

Issues: Assurance; inventory completeness; documented testing; organizational controls.

== Issue J: Recent reports requiring continued investigation (October 2026) ==

[https://bugzilla.mozilla.org/show_bug.cgi?id=2083866 Bug 2083866] records a third-party report that CCADB policy-document disclosures lagged versions published in Netlock's repository. The report also raised the availability of an English policy version and continuity of policy versions. The retrieved preliminary report does not establish every allegation as a completed Mozilla finding. Its observation that a CRL has a twelve-month validity interval is not, by itself, treated here as proof of a violation.

[https://bugzilla.mozilla.org/show_bug.cgi?id=2084949 Bug 2084949] reports use of a Precertificate Signing CA after the 15 March 2026 prohibition. The preliminary report identifies a precertificate signed on 20 October 2026 and states that Netlock confirmed the finding; a subsequent comment confirms receipt and the CA's constrained role while verification was underway. The full affected population and explanation of the missed transition were still being determined in the retrieved record.

These reports add unresolved questions about requirements implementation and disclosure. The cumulative concerns above do not depend on assuming the broadest possible interpretation of either new report.

== Action by another root program ==

On 30 May 2025, Google Chrome announced withdrawal of default trust for newly issued TLS certificates chaining to the NetLock Arany (Class Gold) Főtanúsítvány root. Chrome cited recurring compliance failures, unfulfilled improvement commitments, and insufficient demonstrated progress. Its constraint applies in Chrome 139 and later when a certificate's earliest SCT is after 31 July 2025 at 23:59:59 UTC.

Source: [https://blog.google/security/sustaining-digital-certificate-security-chrome-root-store-changes/ Chrome Root Program announcement].

This is relevant external context. Mozilla's assessment rests on the underlying public record and its own expectations for continued inclusion.

== Cumulative assessment ==

The record supports concern about Netlock's sustained operational and compliance capability across multiple functions. Earlier incidents produced commitments concerning reporting, training, ownership, disclosure checks and technical validation. Later incidents documented recurrence and identified limitations in the controls previously presented as corrective measures.

The concern is therefore broader than the number of individual bugs or the immediate severity of any one profile error. Effective CA operation requires detecting defects, establishing their complete scope, correcting all affected paths, meeting revocation and reporting deadlines, and demonstrating that the corrections continue to work. The recurring combination of incomplete coverage, externally prompted investigation, missed public commitments, and repeated reporting failures undermines confidence that those functions operate reliably.

Netlock has acknowledged failures, completed individual corrective actions, and provided some concrete verification results. Those improvements should be credited. They must also be evaluated against subsequent performance and the repeated failure of prior measures to prevent recurrence. A newly implemented control provides a basis for further verification; implementation alone does not establish sustained effectiveness.

== Related records and scope qualifications ==

* [https://bugzilla.mozilla.org/show_bug.cgi?id=2032939 Bug 2032939] and [https://bugzilla.mozilla.org/show_bug.cgi?id=2033033 Bug 2033033] concern Netlock's dual-purpose-root transition. In Bug 2033033, Mozilla stated that allowing the root to expire on 6 December 2028 satisfied the substantive separation requirement. These records are context, not proof that Netlock has already violated the end-of-2028 deadline.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1824435 Bug 1824435] was resolved INVALID regarding SCTs from an untrusted log. That allegation is not counted as a compliance failure; the separately identified certificateHold issue is addressed in Bug 1830823.
* Bugs 1891331 and 1947691 represent the same delayed-revocation episode. Bugs 1905509 and 1906115 contain related material about the same 2024 reporting-contact problem.
* Root inclusion requests and routine root transitions are not themselves evidence of non-compliance. No assertion of current audit delinquency is made here without the relevant audit records and deadlines being verified.

CA/Maintenance and Enforcement

Bwilson — Wed, 04 Nov 2026 23:19:48 GMT

Issues Lists: Added link to Netlock issues list

← Older revision		Revision as of 23:19, 4 November 2026
Line 96:		Line 96:

	= Issues Lists =		= Issues Lists =
			* https://wiki.mozilla.org/CA/Netlock_Issues
	* https://wiki.mozilla.org/CA/Entrust_Issues		* https://wiki.mozilla.org/CA/Entrust_Issues
	* https://wiki.mozilla.org/CA/e-commerce-monitoring_Issues		* https://wiki.mozilla.org/CA/e-commerce-monitoring_Issues

Foundation/Mozilla Education/Events

JaselleMozEdu — Wed, 04 Nov 2026 14:42:26 GMT

2026 Events and Convenings

← Older revision		Revision as of 14:42, 4 November 2026
Line 1:		Line 1:

	== 2026 Events and Convenings ==		== 2026 Events and Convenings ==
			=== October ===
			{\|
			\|-
			\| '''Mozilla Education at Mozilla Festival 2026 (Barcelona, Spain; 28-30 October 2026; 100 attendees)''' The Mozilla Education team presented at two dedicated sessions during Mozilla Festival. The first session gave a forward-looking overview of future activities, including an interactive design-task workshop. The Compute Project held a discussion session for community members to share their perspectives on successes and challenges in working with compute infrastructure. In addition, the culmination of the Responsible Computing Challenge Buildathon in Kenya saw Maryanne Farida present their project, ‘Hustle Yeta’ providing regulatory alerts for boda boda micro-businesses, enabling drivers to keep up to date with critical legal and tax-related changes.
			The sessions below were also held by our RCC awardees;
			* Dalia Muller - RCC US Alumni; Marooning AI - centering the historical experiences, technologies and ways of knowing of maroons, self-liberated enslaved Africans who created their own autonomous communities on the borders of European empires.
			* Josiah Hester - RCC US 2026; AI is the Next Global Plantation: Unless we Build Indigenous Data Sovereignty, comparing the buildout of AI and AI companies to the global plantation industry of the 18th and 19th centuries that ravaged colonized states around the world.
			'''Key Takeaway:''' The Mozilla Education Team continues to co-design current and future program activities with local communities and movement builders to ensure that those impacted by the future of tech have a say in how it is built.

			\|-

			\|}

	=== September ===		=== September ===

Compatibility/Site Reports Triage

SkySchub — Wed, 04 Nov 2026 14:33:50 GMT

Re-arrange queries for optimized triage(tm)

← Older revision		Revision as of 14:33, 4 November 2026
Line 1:		Line 1:
			== Untriaged ==
			* [https://bugzilla.mozilla.org/buglist.cgi?f10=CP&o12=notregexp&f16=component&resolution=---&o7=notequals&v12=webcompat%3Ablocked&f11=OP&v7=Web%20Compatibility&f9=CP&f6=OP&f18=CP&f13=cf_user_story&f8=keywords&f7=product&o16=equals&f12=keywords&v16=Performance&j15=OR&v13=impact%3A&v8=webcompat%3Asite-report&o8=substring&o13=notsubstring&f15=OP&o17=isnotempty&f4=component&v3=Web%20Compatibility&o3=equals&f17=cf_performance_impact&f5=CP&f2=OP&j1=OR&o4=equals&order=Last%20Updated&f14=CP&n15=1&f1=OP&f3=product&v4=Site%20reports Triage queue]

	== Webcompat Priority: ? ==		== Webcompat Priority: ? ==
	* [https://bugzilla.mozilla.org/buglist.cgi?cf_webcompat_priority=%3F&order=changeddate+DESC&resolution=--- Triage queue]		* [https://bugzilla.mozilla.org/buglist.cgi?cf_webcompat_priority=%3F&order=changeddate+DESC&resolution=--- Triage queue]

	~~== Untriaged ==~~
	* [https://bugzilla.mozilla.org/buglist.cgi?f10=CP&o12=notregexp&f16=component&resolution=---&o7=notequals&v12=webcompat%3Ablocked&f11=OP&v7=Web%20Compatibility&f9=CP&f6=OP&f18=CP&f13=cf_user_story&f8=keywords&f7=product&o16=equals&f12=keywords&v16=Performance&j15=OR&v13=impact%3A&v8=webcompat%3Asite-report&o8=substring&o13=notsubstring&f15=OP&o17=isnotempty&f4=component&v3=Web%20Compatibility&o3=equals&f17=cf_performance_impact&f5=CP&f2=OP&j1=OR&o4=equals&order=Last%20Updated&f14=CP&n15=1&f1=OP&f3=product&v4=Site%20reports Triage queue]

	== Missing Severity ==		== Missing Severity ==

User:SpikeUK1

SpikeUK1 — Wed, 04 Nov 2026 09:21:37 GMT

Account approvals : November 2026: Two likely spammer/s rejected. Backlog zero.

← Older revision		Revision as of 09:21, 4 November 2026
Line 246:		Line 246:
	\|-		\|-
	\| 3<sup>rd</sup> November 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6		\| 3<sup>rd</sup> November 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6
			\|-
			\| 4<sup>th</sup> November 2026 \|\| 0 \|\| 2 \|\| 0 \|\| 0 \|\| 2
	\|}		\|}

BMO/Recent Changes/2026-11

DaveLawrence — Tue, 03 Nov 2026 22:03:23 GMT

Created page with "== 2026-11-03 == [https://github.com/mozilla-bteam/bmo/tree/release-20261103.1 release-20261103.1] * {{bug|2087000}} Sometimes phab "last modified" timestamp updates without actual changes to the revision * {{bug|2081860}} Migrate Bug REST resource to native Mojo API: bug objects (get, search, create, update, possible_duplicates, history) * {{bug|2070239}} Add DB-backed tests for flag-event bugmail recipient selection (prev-status tie-break, flag-type cc_list) * {{bug|2..."

New page

== 2026-11-03 ==

[https://github.com/mozilla-bteam/bmo/tree/release-20261103.1 release-20261103.1]
* {{bug|2087000}} Sometimes phab "last modified" timestamp updates without actual changes to the revision
* {{bug|2081860}} Migrate Bug REST resource to native Mojo API: bug objects (get, search, create, update, possible_duplicates, history)
* {{bug|2070239}} Add DB-backed tests for flag-event bugmail recipient selection (prev-status tie-break, flag-type cc_list)
* {{bug|2082543}} Clean up after the REST-to-Mojo migration: shared helpers in Bugzilla::API::V1::Util

BMO/Recent Changes

DaveLawrence — Tue, 03 Nov 2026 22:03:05 GMT

@@ Line 1: / Line 1: @@
 = Recent Changes =
 == 2026-10-28 ==
@@ Line 37: / Line 45: @@
 * {{bug|2078690}} Migrate User REST resource to native Mojo API: user objects (get, create, update, suggest, whoami, offer_account_by_email)
 * {{bug|2079991}} When one update requests needinfo from several users , the webhook's `event.changes` has a single `flag.needinfo` entry for the last requestee only; the others are dropped.
 = Archive =
 * [[BMO/Recent_Changes/2026-10|2026-10]]
 * [[BMO/Recent_Changes/2026-09|2026-09]]

Support/Firefox159

Kelimutu — Tue, 03 Nov 2026 16:29:38 GMT

Dot releases: adding 159.0.1

← Older revision		Revision as of 16:29, 3 November 2026
Line 22:		Line 22:

	== Dot releases ==		== Dot releases ==
	~~TBD~~
	~~<!--~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! Platform !! Version !! Release date !! Notable fixes !! Unresolved		! Platform !! Version !! Release date !! Notable fixes !! Unresolved
	\|-		\|-
	\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/~~154~~.0.1/releasenotes/ ~~154~~.0.1] \|\| ~~Jan 20~~, 2026 \|\| [https://~~bugzilla~~.mozilla.org/ ~~bugxxxxx], [https://bugzilla.mozilla.org/ bugxxxxx], [https:~~//~~bugzilla.mozilla.org/ bugxxxxx~~] \|\| -		\| Firefox Desktop \|\| [https://www.mozilla.org/firefox/159.0.1/releasenotes/ 159.0.1] \|\| Nov 3, 2026 \|\| Various fixes & [https://www.mozilla.org/security/advisories/mfsa2026-123 security fix] \|\| -
	\|-		\|-
	\| Firefox & Focus for Android \|\| [https://www.mozilla.org/firefox/android/~~154~~.0.1/releasenotes/ ~~1491520~~.1] \|\| ~~Jan 20~~, 2026 \|\| Various ~~stability~~ fixes \|\| -		\| Firefox & Focus for Android \|\| [https://www.mozilla.org/firefox/android/159.0.1/releasenotes/ 159.0.1] \|\| Nov 3, 2026 \|\| Various fixes & [https://www.mozilla.org/security/advisories/mfsa2026-123 security fix] \|\| -
			<!--
	\|-		\|-
	\| Firefox & Focus for iOS \|\| 154.1 \|\| Jan 20, 2026 \|\| Various stability fixes \|\| -		\| Firefox & Focus for iOS \|\| 154.1 \|\| Jan 20, 2026 \|\| Various stability fixes \|\| -
			-->
	\|}		\|}
	~~-->~~

	== Contributor discussions ==		== Contributor discussions ==

User:SpikeUK1

SpikeUK1 — Tue, 03 Nov 2026 10:03:15 GMT

Account approvals : November 2026: Six likely spammer/s rejected. Backlog zero.

← Older revision		Revision as of 10:03, 3 November 2026
Line 244:		Line 244:
	\|-		\|-
	\| 1<sup>st</sup> November 2026 \|\| 0 \|\| 2 \|\| 0 \|\| 0 \|\| 2		\| 1<sup>st</sup> November 2026 \|\| 0 \|\| 2 \|\| 0 \|\| 0 \|\| 2
			\|-
			\| 3<sup>rd</sup> November 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6
	\|}		\|}

Foundation/Mozilla Education

JaselleMozEdu — Mon, 02 Nov 2026 16:50:51 GMT

← Older revision		Revision as of 16:50, 2 November 2026
Line 169:		Line 169:
	*University of Cape Town \| Cape Town \| Malebogo Ngoepe		*University of Cape Town \| Cape Town \| Malebogo Ngoepe
	*University of Witwatersrand \| Johannesburg \| Richard Klein		*University of Witwatersrand \| Johannesburg \| Richard Klein
	*University of the Western Cape \| Cape Town \| ~~Mmaki Jantjies~~		*University of the Western Cape \| Cape Town \| Carolien van den Berg
	*Central University of Technology, Free State \| Bloemfontein \| Luzaan Schlebusch		*Central University of Technology, Free State \| Bloemfontein \| Luzaan Schlebusch
	*University of Pretoria \| Pretoria \| Marlene Holmner		*University of Pretoria \| Pretoria \| Marlene Holmner

Privacy/Docs/How To Triage ETP-Strict Website Breakage

Manuel Bucher — Mon, 02 Nov 2026 09:36:37 GMT

Putting diagnosis into bug: also make the other two configurations easy to copy

← Older revision		Revision as of 09:36, 2 November 2026
Line 67:		Line 67:
	# Depending on the [https://docs.google.com/document/d/15Nw7OAMzsHxR4hPu5ZQ117w-KrDVZd3ZE-ISQ5tdSOE/edit?tab=t.0#heading=h.1rlefy7l7tx2 WebCompat Classification Criteria] to add either '''<span style="user-select: all;"><code>[exception-baseline]</code></span>''' or '''<span style="user-select: all;"><code>[exception-convenience]</code></span>''' to the whiteboard.		# Depending on the [https://docs.google.com/document/d/15Nw7OAMzsHxR4hPu5ZQ117w-KrDVZd3ZE-ISQ5tdSOE/edit?tab=t.0#heading=h.1rlefy7l7tx2 WebCompat Classification Criteria] to add either '''<span style="user-select: all;"><code>[exception-baseline]</code></span>''' or '''<span style="user-select: all;"><code>[exception-convenience]</code></span>''' to the whiteboard.
	# Add necessary URLs to unblock into the User Story as the format '''<span style="user-select: all;"><code>trackers-blocked:xyz.com,*.abc.com</code></span>'''.		# Add necessary URLs to unblock into the User Story as the format '''<span style="user-select: all;"><code>trackers-blocked:xyz.com,*.abc.com</code></span>'''.
	# Add classifier features into the User Story as the format <span style="user-select: all;"><code>classifier-features:tracking-protection,emailtracking-protection,socialtracking-protection,fingerprinting-protection</code></span> to indicate which features to unblock. See <span style="user-select: all;"><code>about:url-classifier</code></span> for available lists. Usually it is '''<span style="user-select: all;"><code>classifier-features:tracking-protection</code></span>'''		# Add classifier features into the User Story as the format <span style="user-select: all;"><code>classifier-features:tracking-protection,emailtracking-protection,socialtracking-protection,fingerprinting-protection</code></span> to indicate which features to unblock. See <span style="user-select: all;"><code>about:url-classifier</code></span> for available lists. Usually it is
			#* '''<span style="user-select: all;"><code>classifier-features:tracking-protection</code></span>''',
			#* <span style="user-select: all;"><code>classifier-features:tracking-protection,socialtracking-protection</code></span> or
			#* <span style="user-select: all;"><code>classifier-features:tracking-protection,emailtracking-protection</code></span>.

	When reopening bugs due to privious diagnosis not really unbreaking the reported behavior, remove <span style="user-select: all;"><code>[privacy-team:diagnosed]</code></span> from the whiteboard to put the bug back into the [[#Triage_Quick_Links\|Needs list of trackers blocked]]-list		When reopening bugs due to privious diagnosis not really unbreaking the reported behavior, remove <span style="user-select: all;"><code>[privacy-team:diagnosed]</code></span> from the whiteboard to put the bug back into the [[#Triage_Quick_Links\|Needs list of trackers blocked]]-list

User:SpikeUK1

SpikeUK1 — Sun, 01 Nov 2026 13:14:47 GMT

Account approvals : November 2026: One more likely spammer rejected. Backlog zero.

← Older revision		Revision as of 13:14, 1 November 2026
(One intermediate revision by the same user not shown)
Line 235:		Line 235:
	\|-		\|-
	\| 31<sup>st</sup> October 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6		\| 31<sup>st</sup> October 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6
			\|}

			== Account approvals : November 2026 ==

			{\| class="wikitable"
			\|-
			! Date !! Approved !! Spam !! Rejected !! Held !! Total
			\|-
			\| 1<sup>st</sup> November 2026 \|\| 0 \|\| 2 \|\| 0 \|\| 0 \|\| 2
	\|}		\|}

Bugzilla:Review Queue

Justdave — Sun, 01 Nov 2026 05:53:29 GMT

5.2.1 Cohort Release Blockers: update status

← Older revision		Revision as of 05:53, 1 November 2026
Line 6:		Line 6:
	* [https://github.com/bugzilla/harmony/pull/182 <nowiki>[bugzilla/harmony] [harmony] Bug 2066699: Add extension hook: user_preferences_settings (#182)</nowiki>] - prerequisite for #156		* [https://github.com/bugzilla/harmony/pull/182 <nowiki>[bugzilla/harmony] [harmony] Bug 2066699: Add extension hook: user_preferences_settings (#182)</nowiki>] - prerequisite for #156
	* [https://github.com/bugzilla/harmony/pull/156 <nowiki>[bugzilla/harmony] [harmony] Bug 1983391: Add a donation banner to the home page (#156)</nowiki>]		* [https://github.com/bugzilla/harmony/pull/156 <nowiki>[bugzilla/harmony] [harmony] Bug 1983391: Add a donation banner to the home page (#156)</nowiki>]
			* [https://github.com/bugzilla/bugzilla/pull/255 <nowiki>[bugzilla/bugzilla] [5.2] Bug 2066699: Add extension hook: user_preferences_settings (#255)</nowiki>] - prerequisite for #228
			* [https://github.com/bugzilla/bugzilla/pull/228 <nowiki>[bugzilla/bugzilla] [5.2] Bug 1983391: Add a donation banner to the home page (#228)</nowiki>]
	* [https://github.com/bugzilla/harmony/pull/185 <nowiki>[bugzilla/harmony] [harmony] Bug 2069203: Fix potential loading issues when loading Oracle database driver (#185)</nowiki>] - this already landed on the 5.2 branch and the harmony counterpart never got reviewed.		* [https://github.com/bugzilla/harmony/pull/185 <nowiki>[bugzilla/harmony] [harmony] Bug 2069203: Fix potential loading issues when loading Oracle database driver (#185)</nowiki>] - this already landed on the 5.2 branch and the harmony counterpart never got reviewed.
	* [https://github.com/bugzilla/harmony/pull/186 <nowiki>[bugzilla/harmony] Bug 2059981: Hide the "OAuth2 Clients" item from admin utilities if the feature isn't available. (#186)</nowiki>]
	* [https://github.com/bugzilla/bugzilla-security/issues?q=is%3Aopen%20is%3Apr Every PR in the private Security repo] that isn't already tagged as Approved		* [https://github.com/bugzilla/bugzilla-security/issues?q=is%3Aopen%20is%3Apr Every PR in the private Security repo] that isn't already tagged as Approved

User:Rolandtb/strings-153.6.0-159.0-160.0-account-settings

Rolandtb — Sat, 31 Oct 2026 20:16:52 GMT

copied from https://github.com/thunderbird/sumo-linter/blob/main/tools/ui-strings/strings-153.6.0-159.0-160.0-account-settings.mediawiki

New page

* copied from: https://github.com/thunderbird/sumo-linter/blob/main/tools/ui-strings/strings-153.6.0-159.0-160.0-account-settings.mediawiki
Account Settings texts that changed between Thunderbird ESR 153.6.0, Release 159.0 and Beta 160.0, in en-US. — means the text does not exist in that version. Bold marks the words that changed from the previous version. A cell with several lines lists all the texts that changed together for one setting, and gets no bold. "Changed in" names the versions that changed the row. "same as 159" means that version did not change the text. Made by tools/ui-strings/l10n_tables.py (sumo-linter #19, #23).

{| class="wikitable sortable"
! Changed in !! ESR 153.6.0 !! Release 159.0 !! Beta 160.0
|-
| 160 || Allow immediate server notifications when new messages arrive || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || — || — || style="background:#fff3c4" | Writing emails
|-
| 160 || — || — || style="background:#fff3c4" | Address autocomplete
|-
| 160 || — || — || style="background:#fff3c4" | Delete immediately
|-
| 160 || — || — || style="background:#fff3c4" | Server settings
|-
| 160 || Security Settings || ''same as 153'' || style="background:#fff3c4" | Security '''and sign-in'''
|-
| 160 || When I delete a message: Check for new messages at startup Remove it immediately Just mark it as deleted || ''same as 153'' || style="background:#fff3c4" | Check for new messages when Thunderbird opens Deleting messages Get new messages when they arrive on the server Mark as deleted without moving Message checking
|-
| 160 || When sending messages, automatically: Leave the address field blank to always show the address row when starting a new message. || ''same as 153'' || style="background:#fff3c4" | Other folder: Note: Checking these boxes adds automatic Cc/Bcc rows when composing new messages. Sent folder on: Other folder
|-
| 160 || Message Archives || ''same as 153'' || style="background:#fff3c4" | Archives folder on: Message archives
|-
| 160 || Show confirmation dialog when messages are saved Drafts and Templates || ''same as 153'' || style="background:#fff3c4" | Show a confirmation when messages are saved Drafts and templates Drafts folder on: Templates folder on:
|-
| 160 || Compose messages in HTML format || ''same as 153'' || style="background:#fff3c4" | '''Write''' messages in '''rich text (HTML)'''
|-
| 160 || When looking up addresses: Use a different LDAP server: Use my global LDAP server preferences for this account || ''same as 153'' || style="background:#fff3c4" | When looking up contacts for this account:
|-
| 159 || Spam Settings Do not automatically mark mail as spam if the sender is in: Enable adaptive spam controls for this account If enabled, you must first train Thunderbird to identify spam by using the Spam toolbar button to mark messages as spam or not. You need to identify both spam and non spam messages. After that Thunderbird will be able to mark spam automatically. || style="background:#fff3c4" | Manage spam Turn on automatic spam detection for this account Trust email addresses in these address books: || ''same as 159''
|-
| 159 || Global Spam Settings… || style="background:#fff3c4" | Global '''spam settings…''' || ''same as 159''
|-
| 159 || Destination and Retention || style="background:#fff3c4" | — || —
|-
| 160 || Keep messages in all folders for this account on this computer Note: Changing this affects all folders in this account. To set individual folders, use the Advanced… button. Message Synchronizing || ''same as 153'' || style="background:#fff3c4" | Offline message storage Applies to all folders in this account. Save copies of all folders and messages on this computer for offline use
|-
| 160 || Don't download messages larger than To save disk space, downloading messages from the server and keeping local copies for offline use can be restricted by age or size. || ''same as 153'' || style="background:#fff3c4" | Set rules to automatically delete old emails from both this computer and the mail server to free up space. Download limits Choose which messages to store locally on this computer: Set deletion rules Skip downloading messages larger than:
|-
| 160 || Preferred encryption technology: Default settings for sending messages Attach my public key when adding an OpenPGP digital signature Send OpenPGP public key(s) in the email headers for compatibility with Autocrypt Disable encryption for new messages You will be able to disable encryption for individual messages. Enable encryption for new messages Store draft messages in encrypted format Encrypt the subject of OpenPGP messages Sign unencrypted messages A digital signature allows recipients to verify that the message was sent by you and its content was not changed. Encrypted messages are always signed by default. || ''same as 153'' || style="background:#fff3c4" | Advanced encryption settings Do not encrypt new messages by default Encrypt new messages by default Preferred encryption technology Digitally sign unencrypted messages Default message encryption
|-
| 160 || Addressing || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || Composition || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || "Archives" Folder on: || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || "Drafts" Folder on: || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || "Sent" Folder on: || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || "Templates" Folder on: || ''same as 153'' || style="background:#fff3c4" | —
|-
| 159 || Username: || style="background:#fff3c4" | — || —
|-
| 159 || Notify on new Mail || style="background:#fff3c4" | — || —
|-
| 159 || Proxy Settings: || style="background:#fff3c4" | — || —
|-
| 159 || Change… || style="background:#fff3c4" | — || —
|-
| 159 || Show newsgroup names in the Mail Folder pane as: || style="background:#fff3c4" | — || —
|-
| 159 || Abbreviate names (For example, 'n.p.m.mail-news') || style="background:#fff3c4" | — || —
|-
| 159 || Full names (For example, 'netscape.public.mozilla.mail-news') || style="background:#fff3c4" | — || —
|-
| 160 || Clean up ("Expunge") Inbox on Exit || ''same as 153'' || style="background:#fff3c4" | —
|-
| 159 || Set Personal Key… || style="background:#fff3c4" | — || —
|-
| 159 || Personal key for encryption and digital signing: || style="background:#fff3c4" | — || —
|-
| 159 || Digital Signing || style="background:#fff3c4" | — || —
|-
| 159 || Thunderbird Settings || style="background:#fff3c4" | — || —
|-
| 160 || — || — || style="background:#fff3c4" | Permanently remove deleted messages from the Inbox on exit
|-
| 160 || — || — || style="background:#fff3c4" | Offline folder settings…
|-
| 160 || — || — || style="background:#fff3c4" | Sign-in method:
|-
| 160 || — || — || style="background:#fff3c4" | Use global LDAP directory settings
|-
| 160 || — || — || style="background:#fff3c4" | Use a specific LDAP directory server:
|-
| 159 || — || style="background:#fff3c4" | OAuth2 settings provided by extension: <a data-l10n-name="extension">{ $extensionName }</a> || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Authorization endpoint: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Client ID: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Client secret: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Issuer identifier: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Scopes: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Token endpoint: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Use custom OAuth2 settings || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Use PKCE || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Use system web browser || ''same as 159''
|-
| 160 || — || — || style="background:#fff3c4" | Attach the public key for this identity when digitally signing messages
|-
| 160 || — || — || style="background:#fff3c4" | Encrypt message subject line
|-
| 160 || — || — || style="background:#fff3c4" | Encryption can be turned off for individual messages while writing emails.
|-
| 160 || — || — || style="background:#fff3c4" | Include this account’s public key in message headers (for Autocrypt compatibility)
|-
| 160 || — || — || style="background:#fff3c4" | Proves to recipients that the message came from you and was not altered in transit. Encrypted messages are signed by default.
|-
| 159 || The attachment ‘{ $name }’ you are opening appears to be an OpenPGP key file. Click ‘Import’ to import the keys contained or ‘View’ to view the file contents in a browser window || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | The attachment ‘{ $name }’ appears to be an OpenPGP key file. Do you want to import the keys it contains? || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | &Open… || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | &Save || ''same as 159''
|-
| 159 || &View || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Version || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Generate PQC Encryption Subkey || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | The key, or subordinate parts of the key, could not be unlocked. || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Generate an encryption subkey using post-quantum cryptography (PQC)? Generation may take several minutes. || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | The PQC encryption subkey could not be generated. || ''same as 159''
|-
| 160 || — || — || style="background:#fff3c4" | Choose where to save copies of sent messages, and set up automatic Cc/Bcc rules
|-
| 160 || — || — || style="background:#fff3c4" | Copies and folders
|-
| 159 || Selection || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Detecting spam || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Storage and deletion || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | When turned on, Thunderbird learns from the messages you mark as spam or not spam. The more you train it, the better Thunderbird gets at detecting spam. || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Encryption algorithm: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | { $algorithm } ({ $keySize }-bit) || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Algorithms || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Signature Digest algorithm: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Key Encryption algorithm: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Signature algorithm: || ''same as 159''
|}

User:Rolandtb/strings-153.6.0-159.0-160.0-settings

Rolandtb — Sat, 31 Oct 2026 20:13:13 GMT

copy/pasted from https://github.com/thunderbird/sumo-linter/blob/main/tools/ui-strings/strings-153.6.0-159.0-160.0-settings.mediawiki

New page

* (manually copied from: https://github.com/thunderbird/sumo-linter/blob/main/tools/ui-strings/strings-153.6.0-159.0-160.0-settings.mediawiki )
Settings texts that changed between Thunderbird ESR 153.6.0, Release 159.0 and Beta 160.0, in en-US. — means the text does not exist in that version. Bold marks the words that changed from the previous version. A cell with several lines lists all the texts that changed together for one setting, and gets no bold. "Changed in" names the versions that changed the row. "same as 159" means that version did not change the text. Made by tools/ui-strings/l10n_tables.py (sumo-linter #19, #23).

{| class="wikitable sortable"
! Changed in !! ESR 153.6.0 !! Release 159.0 !! Beta 160.0
|-
| 159 || When Thunderbird launches, show the Start Page in the message area || style="background:#fff3c4" | '''Show''' the Start Page '''when Thunderbird opens''' || ''same as 159''
|-
| 159 || Restore Default || style="background:#fff3c4" | Restore '''default''' || ''same as 159''
|-
| 159 || Always check to see if Thunderbird is the default mail client on startup System Integration || style="background:#fff3c4" | System settings || ''same as 159''
|-
| 159 || Check Now… Always perform this check when starting Thunderbird Use Thunderbird as the default client for: || style="background:#fff3c4" | Edit defaults… Use Thunderbird as the default app for: || ''same as 159''
|-
| 159 || Use autoscrolling || style="background:#fff3c4" | '''Enable auto-scrolling''' || ''same as 159''
|-
| 159 || Choose the languages used to display menus, messages, and notifications from Thunderbird. || style="background:#fff3c4" | Choose the language used for menus, buttons, and notifications. Display language || ''same as 159''
|-
| 159 || Set Alternatives… || style="background:#fff3c4" | '''Manage languages…''' || ''same as 159''
|-
| 159 || Font Control Allow messages to use other fonts Use fixed width font for plain text messages || style="background:#fff3c4" | Allow incoming messages to use their own fonts Display plain text messages in a fixed-width font Message font permissions Text & font options Customize fonts… || ''same as 159''
|-
| 159 || App Icon Options… || style="background:#fff3c4" | App '''icon options…''' || ''same as 159''
|-
| 159 || Animate the app icon when a new message arrives Count of new messages Count of unread messages Badge app icon with: App icon options You can disable the badge on the Notification pane of System Settings. || style="background:#fff3c4" | Show a badge for Animate the app icon for new messages App icon notification settings Notification badges can also be turned on or off in the computer’s system settings. Total new messages Total unread messages When a new message arrives: || ''same as 159''
|-
| 159 || Change preferences for the app icon Incoming Mails When new messages arrive: || style="background:#fff3c4" | Show an alert for new emails || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Customize alerts… || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Use custom sound for alerts || ''same as 159''
|-
| 159 || Files & Attachments || style="background:#fff3c4" | Files & '''attachments''' || ''same as 159''
|-
| 159 || Filter content types and actions || style="background:#fff3c4" | Select what files are saved and where they are saved on your computer. Search types of content || ''same as 159''
|-
| 159 || Content Type || style="background:#fff3c4" | Content '''type''' || ''same as 159''
|-
| 159 || Tags can be used to categorize and prioritize your messages. || style="background:#fff3c4" | '''Use tags''' to categorize and prioritize messages. || ''same as 159''
|-
| 159 || View attachments inline || style="background:#fff3c4" | '''Show''' attachments '''inside the message body''' || ''same as 159''
|-
| 159 || Always underline links Reading & Display || style="background:#fff3c4" | Reading & viewing || ''same as 159''
|-
| 159 || Immediately on display || style="background:#fff3c4" | Immediately '''when opened''' || ''same as 159''
|-
| 159 || After displaying for || style="background:#fff3c4" | — || —
|-
| 159 || When displaying quoted plain text messages: || style="background:#fff3c4" | '''Quoted''' text '''formatting''' || ''same as 159''
|-
| 159 || Plain Text Messages || style="background:#fff3c4" | Plain '''text messages''' || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Message list || ''same as 159''
|-
| 159 || Show only display name for people in my address book || style="background:#fff3c4" | — || —
|-
| 159 || Experimental feature based on Gloda, use it at your own risk Enable conversation view || style="background:#fff3c4" | This is an early preview feature. It groups related messages together, but it might not always work as expected. Show conversation view || ''same as 159''
|-
| 159 || Leave it in my Inbox If I’m not in the To or Cc of the message: When I receive a request for a return receipt: Return Receipts When sending messages, always request a return receipt If the sender is outside my domain: || style="background:#fff3c4" | — || —
|-
| 159 || Enable dark message mode Force the message body to follow dark themes Message reader style || style="background:#fff3c4" | Use dark mode for message text Message appearance Applies a dark background to all incoming messages, even if the sender formatted them in light colors. || ''same as 159''
|-
| 159 || Show a toggle in the message header to quickly disable the dark message mode || style="background:#fff3c4" | '''Lets you quickly switch an email back''' to '''light''' mode '''while reading, without changing your main settings.''' || ''same as 159''
|-
| 159 || Folder Management Options Options for listing and sorting folders where messages were recently moved to. Recent Destinations || style="background:#fff3c4" | Folder settings Controls how recently used folders appear when moving messages. Recent folders || ''same as 159''
|-
| 159 || Thunderbird is being managed by your organization. || style="background:#fff3c4" | Thunderbird is managed by '''an''' organization. || ''same as 159''
|-
| 159 || Show Update History || style="background:#fff3c4" | Show '''history''' || ''same as 159''
|-
| 159 || Allow Thunderbird to Automatically install updates (recommended: improved security) || style="background:#fff3c4" | Keeps Thunderbird secure with the latest security fixes. Automatically install updates (recommended) Update settings || ''same as 159''
|-
| 159 || Check for updates, but let me choose whether to install them || style="background:#fff3c4" | Check for updates, but '''ask before installing''' || ''same as 159''
|-
| 159 || Offline Settings || style="background:#fff3c4" | Offline '''settings''' || ''same as 159''
|-
| 159 || Automatically follow detected online state Download messages for offline use when going offline? Send unsent messages when going online? Manual state when starting up: Ask me for online state Remember previous online state Configure offline settings || style="background:#fff3c4" | Automatically switch modes when an internet connection is found Ask before downloading Yes, download automatically No, do not download Do you want to download messages to read offline? Ask before sending No, keep in Outbox Yes, send automatically When opening Thunderbird: Ask whether to connect online Use the last-used connection mode Start offline Start online Offline mode Offline settings || ''same as 159''
|-
| 159 || Connection Settings || style="background:#fff3c4" | Connection '''settings''' || ''same as 159''
|-
| 159 || Configure Proxies to Access the Internet Connections to localhost, 127.0.0.1/8, and ::1 are never proxied. No proxy for: Also use this proxy for HTTPS Do not prompt for authentication if password is saved Proxy DNS when using SOCKS v5 Automatic proxy configuration URL: Manual proxy configuration: Auto-detect proxy settings for this network Network & Disk Space Configure how Thunderbird connects to the Internet || style="background:#fff3c4" | Internet connection & proxy Local network connections (like localhost) never use a proxy. Do not use a proxy for these addresses: Automatically log in if a password is saved Automatic setup script URL: Automatically detect network proxy Use this proxy for secure web addresses (HTTPS) Manual proxy setup: Route domain requests (DNS) through SOCKS v5 proxy Control how Thunderbird connects to the internet. Connection options… Network and storage || ''same as 159''
|-
| 159 || Clear cache on shutdown || style="background:#fff3c4" | Clear '''temporary files when Thunderbird closes''' || ''same as 159''
|-
| 159 || Clear Now Disk Space || style="background:#fff3c4" | Clear temporary files Temporary storage || ''same as 159''
|-
| 159 || Override automatic cache management || style="background:#fff3c4" | '''Manually set storage limits for temporary files''' || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | MB of space for temporary files || ''same as 159''
|-
| 159 || Compact all folders when it will save over || style="background:#fff3c4" | '''Remove data from''' folders when '''they have already been deleted to free up storage''' || ''same as 159''
|-
| 159 || Ask every time before compacting || style="background:#fff3c4" | Ask before '''cleaning up folders''' || ''same as 159''
|-
| 159 || Enable Global Search and Indexer || style="background:#fff3c4" | Turn on search across all email accounts Search & performance || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Show search results as a plain list || ''same as 159''
|-
| 159 || Config Editor… || style="background:#fff3c4" | '''Advanced settings''' || ''same as 159''
|-
| 159 || Define the color used for primary buttons and highlighted elements: || style="background:#fff3c4" | '''Select''' color for primary '''button''' and '''highlights''' || ''same as 159''
|-
| 159 || Use hardware acceleration when available File per folder (mbox) Message Store Type for new accounts: || style="background:#fff3c4" | Use graphics acceleration for smoother scrolling and performance Single file per folder (mbox) Storage format for new accounts: || ''same as 159''
|-
| 159 || Auto hide tab bar Hide system window titlebar || style="background:#fff3c4" | Automatically hides tabs until you open a second tab. Removes the top bar showing the window name to save screen space Hide title bar || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Card view Select view style: || ''same as 159''
|-
| 159 || Row Count: || style="background:#fff3c4" | Row '''count:''' || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Card view options || ''same as 159''
|-
| 159 || Sorting and Threading || style="background:#fff3c4" | Sorting and '''threading''' || ''same as 159''
|-
| 159 || Define the default sorting and threading options for newly created folders. || style="background:#fff3c4" | '''Select''' default sorting and threading options for '''new folders''' || ''same as 159''
|-
| 159 || Default Sort Order: || style="background:#fff3c4" | Default '''sort order''' || ''same as 159''
|-
| 159 || New messages at the bottom New messages at the top Default Sort by: || style="background:#fff3c4" | Sort messages by: Newest messages at the top Newest messages at the bottom || ''same as 159''
|-
| 159 || All existing folders Propagate threading and sorting settings to: || style="background:#fff3c4" | Apply these view settings to: All folders and subfolders || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Select folders || ''same as 159''
|-
| 159 || Forward messages: || style="background:#fff3c4" | Writing emails Inside the message (inline) Forward messages as: || ''same as 159''
|-
| 159 || add extension to file name || style="background:#fff3c4" | — || —
|-
| 159 || Auto Save every || style="background:#fff3c4" | '''Automatically save a draft''' every || ''same as 159''
|-
| 159 || Download More Dictionaries || style="background:#fff3c4" | Download '''more dictionaries''' || ''same as 159''
|-
| 159 || HTML Style || style="background:#fff3c4" | '''Message formatting''' || ''same as 159''
|-
| 159 || Enable spellcheck as you type || style="background:#fff3c4" | — || —
|-
| 159 || Use reader’s default colors || style="background:#fff3c4" | '''Ignore sender fonts and''' colors || ''same as 159''
|-
| 159 || Use Paragraph format instead of Body Text by default || style="background:#fff3c4" | '''Pressing Enter starts a new paragraph with extra spacing''' || ''same as 159''
|-
| 159 || Sending Format || style="background:#fff3c4" | Sending '''format''' || ''same as 159''
|-
| 159 || If no styling is used in the message, send Plain Text. Otherwise, send HTML with a Plain Text fallback. The recipient’s email application will determine which version to show. Both HTML and Plain Text Some recipients may not be able to read the message without a Plain Text fallback. Only HTML Some styling will be converted into a plain alternative, while other composition features will be disabled. Only Plain Text || style="background:#fff3c4" | Send formatted text if you add styles (like bold or links), or plain text if you don’t. Automatic (recommended) Always sends both versions so the recipient’s email app can choose which one to display. Both rich text (HTML) and plain text Keeps custom fonts, colors, and images, but some older email apps may not display it properly. Rich text (HTML) only Removes all formatting, colors, and images. Best for simple text emails that work everywhere. Plain text only || ''same as 159''
|-
| 159 || When addressing messages, look for matching entries in: || style="background:#fff3c4" | When typing a recipient’s name or email, look for matches in: Address autocomplete || ''same as 159''
|-
| 159 || Directory Server: || style="background:#fff3c4" | Directory '''server''' || ''same as 159''
|-
| 159 || Local Address Books || style="background:#fff3c4" | '''Company or network directory''' || ''same as 159''
|-
| 159 || Automatically add outgoing email addresses to my: || style="background:#fff3c4" | Where new contacts are saved when created manually or added from emails. Automatically save outgoing email addresses to: || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Where new contacts are saved from emails. Save manually added contacts to: || ''same as 159''
|-
| 159 || Edit Directories… || style="background:#fff3c4" | '''Manage directories…''' || ''same as 159''
|-
| 159 || Default startup directory in the address book window: || style="background:#fff3c4" | '''Show''' directory in the address book '''window when opening Thunderbird''' || ''same as 159''
|-
| 159 || Offer to share for files larger than || style="background:#fff3c4" | Offer to share files '''by link when they exceed:''' || ''same as 159''
|-
| 159 || Attachment Reminder Keywords || style="background:#fff3c4" | Attachment '''reminder keywords''' || ''same as 159''
|-
| 159 || Thunderbird will warn you about missing attachments if you’re about to send an email containing one of these keywords. || style="background:#fff3c4" | '''Edit keywords…''' || ''same as 159''
|-
| 159 || Learn more about the privacy issues of remote content Allow remote content in messages || style="background:#fff3c4" | Email content Allow remote content (images and styles) How remote content affects privacy || ''same as 159''
|-
| 159 || Web Content || style="background:#fff3c4" | Web '''content''' || ''same as 159''
|-
| 159 || From visited || style="background:#fff3c4" | From visited '''sites only''' || ''same as 159''
|-
| 159 || Remove All Cookies || style="background:#fff3c4" | Remove '''all''' Cookies || ''same as 159''
|-
| 159 || { $count -> [one] Remove Selected *[other] Remove Selected } || style="background:#fff3c4" | { $count -> [one] Remove '''selected''' *[other] Remove '''selected''' } || ''same as 159''
|-
| 159 || Cookie Name || style="background:#fff3c4" | Cookie '''name''' || ''same as 159''
|-
| 159, 160 || The following cookies are stored on your computer: || style="background:#fff3c4" | The following cookies are stored on your computer: Cookies are stored on this computer || style="background:#fff3c4" | Cookies are stored on this computer
|-
| 159 || Tell websites not to sell or share my data || style="background:#fff3c4" | '''Ask''' websites not to sell or share '''personal''' data || ''same as 159''
|-
| 159 || Saved Passwords… Thunderbird can remember passwords for all of your accounts. || style="background:#fff3c4" | Thunderbird can save passwords for registered accounts. View Saved Passwords… || ''same as 159''
|-
| 159 || A Primary Password protects all your passwords, but you must enter it once per session. Use a Primary Password || style="background:#fff3c4" | A Primary Password protects all passwords and is entered once per session. Use Primary Password || ''same as 159''
|-
| 159 || When Thunderbird determines that they are spam || style="background:#fff3c4" | When detected automatically by Thunderbird When marked manually || ''same as 159''
|-
| 159 || Set your default spam settings. Account-specific spam settings can be configured in Account Settings. || style="background:#fff3c4" | '''These''' settings '''apply to all accounts. Individual account options''' can be '''changed''' in Account Settings. || ''same as 159''
|-
| 159 || Enable adaptive spam filter logging || style="background:#fff3c4" | '''Keep a log of automatic''' spam '''detection''' || ''same as 159''
|-
| 159 || Delete them Move them to the account’s “Spam” folder || style="background:#fff3c4" | Delete immediately Move to the Spam folder || ''same as 159''
|-
| 159 || We strive to provide you with choices and collect only what we need to provide and improve Thunderbird for everyone. We always ask permission before receiving personal information. Thunderbird Data Collection and Use Privacy Notice || style="background:#fff3c4" | Thunderbird is built by a global community. Sharing anonymous performance data helps us fix bugs faster and make the app faster for everyone. Read our privacy policy || ''same as 159''
|-
| 159 || Thunderbird can make it easy for antivirus software to analyze incoming mail messages for viruses before they are stored locally. Allow antivirus clients to quarantine individual incoming messages || style="background:#fff3c4" | Allows antivirus software to check incoming messages individually before they are saved to your computer. Allow antivirus software to isolate infected incoming emails || ''same as 159''
|-
| 159 || Scam Detection || style="background:#fff3c4" | Scam '''detection''' || ''same as 159''
|-
| 159 || Thunderbird can analyze messages for suspected email scams by looking for common techniques used to deceive you. Tell me if the message I’m reading is a suspected email scam || style="background:#fff3c4" | Thunderbird checks messages for phishing links and common signs of email scams. Warn when reading an email that looks like a scam || ''same as 159''
|-
| 159 || Query OCSP responder servers to confirm the current validity of certificates || style="background:#fff3c4" | '''Check certificate validation''' servers '''(OCSP)''' to confirm certificates '''are still correct.''' || ''same as 159''
|-
| 159 || Ask me every time Select one automatically When a server requests my personal certificate: || style="background:#fff3c4" | Ask every time Choose a certificate automatically When a server asks for a certificate to verify your identity: Security certificates || ''same as 159''
|-
| 159 || Automatic Use of Encryption || style="background:#fff3c4" | Automatic '''use''' of '''encryption''' || ''same as 159''
|-
| 159 || Thunderbird can assist by automatically enabling or disabling encryption while composing an email. Auto enabling/disabling is based on the availability of valid and accepted correspondents’ keys or certificates. || style="background:#fff3c4" | Thunderbird can turn encryption on if valid accepted keys or certificates are available for all recipients of a message. Note: You can also manually turn encryption on or off while writing a message. Replying to an encrypted messages always turns on encryption. || ''same as 159''
|-
| 159 || Email End-To-End Encryption || style="background:#fff3c4" | Email '''end-to-end encryption''' || ''same as 159''
|-
| 159 || Set up email accounts and identities for End-To-End Encryption in the <a data-l10n-name="account-settings-url">Account Settings</a>. || style="background:#fff3c4" | '''Encrypted emails can only be read by you and your recipients.''' Set up email accounts and identities for '''end-to-end encryption''' in the <a data-l10n-name="account-settings-url">Account '''settings</a>.''' || ''same as 159''
|-
| 159 || Automatically disable encryption when recipients change and encryption is no longer possible Automatically enable encryption when possible Automatic decisions may be overridden by manually enabling or disabling encryption when composing a message. Note: encryption is always automatically enabled when replying to an encrypted message. || style="background:#fff3c4" | Automatically turn off encryption when recipients change and encryption is no longer possible Automatically turn on encryption when possible || ''same as 159''
|-
| 159 || Show a notification whenever encryption is disabled automatically || style="background:#fff3c4" | Show a notification whenever encryption is '''turned off''' automatically || ''same as 159''
|-
| 159 || Thunderbird decides when to use secure DNS to protect your privacy. Use your default DNS resolver || style="background:#fff3c4" | Thunderbird automatically encrypts address lookups when available. Switches back to standard network lookups if there’s a connection issue or if a VPN/managed network requires it. Automatic protection (Recommended) || ''same as 159''
|-
| 159 || Domain Name System (DNS) over HTTPS sends your request for a domain name through an encrypted connection, providing a secure DNS and making it harder for others to see which website you’re about to access. DNS over HTTPS || style="background:#fff3c4" | Secure DNS encrypts the lookup requests Thunderbird sends to find websites, keeping your browsing activity private from any network monitoring. Secure DNS (DNS over HTTPS) || ''same as 159''
|-
| 159 || Increased Protection || style="background:#fff3c4" | Increased '''protection''' || ''same as 159''
|-
| 159 || You control when to use secure DNS and choose your provider. Max Protection Thunderbird will always use secure DNS. You’ll see a security risk warning before we use your system DNS. || style="background:#fff3c4" | Always uses chosen provider. Uses standard connection only if secure provider fails. Strictly requires encrypted DNS. Websites will not load if secure connection fails. Uses standard internet provider or network to look up web addresses Maximum protection || ''same as 159''
|-
| 159 || Set timezone manually Use system timezone || style="background:#fff3c4" | Automatically detect timezone Manually set timezone || ''same as 159''
|-
| 159 || When a Reminder is Due: || style="background:#fff3c4" | When a '''reminder''' is '''due:''' || ''same as 159''
|-
| 159 || Create a QR code to export your accounts Quickly transfer your account settings from desktop to mobile by generating a QR code. Select which accounts to include, decide if you want to transfer your password, and scan the code with your mobile device. Fast, secure, and simple. Don’t have Thunderbird on mobile yet? <a data-l10n-name="app-link">Get it on Google Play</a> Export accounts to Thunderbird Mobile || style="background:#fff3c4" | Transfer your email accounts from this computer to Thunderbird on your phone using a QR code. <a data-l10n-name="app-link">Get Thunderbird on Google Play</a> Export to Thunderbird mobile Select accounts to export: || ''same as 159''
|-
| 159 || Not seeing all your accounts? Some accounts may be disabled because they are not supported by Thunderbird for Android. <a data-l10n-name="account-support-link">Support</a> Select which accounts to export: || style="background:#fff3c4" | Missing an account? Accounts that are not supported on Thunderbird for Android cannot be selected. <a data-l10n-name="account-support-link">Learn which account types are supported</a> || ''same as 159''
|-
| 159 || Include all accounts passwords Some of your accounts use an authentication method that may require re-authentication on your mobile device. You may need to enter your passwords again during this process. By scanning the following QR codes, your account settings—including your email and password—will be transferred securely. We do not collect, store, or share any of this data during the process. The transfer occurs directly between your devices. For your security, please ensure you are in a private setting and only scan QR codes from trusted sources. || style="background:#fff3c4" | Include account passwords in the QR code Private transfer: Your settings and passwords move directly from this computer to your phone. Nothing is sent to or stored on Mozilla servers. Tip: Keep your screen hidden from others while the QR code is displayed. || ''same as 159''
|-
| 159 || Move it to my “Sent” folder || style="background:#fff3c4" | Read receipts Leave in Inbox Move to Sent folder If not listed in To or CC field: When a sender requests a return receipt: Always request a return receipt when sending emails If sender is outside company or domain: || ''same as 159''
|-
| 160 || The following applications can be used to handle %S. || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || %S content || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || %S links || ''same as 153'' || style="background:#fff3c4" | —
|-
| 160 || — || — || style="background:#fff3c4" | The following applications can be used to handle { $description } content.
|-
| 160 || — || — || style="background:#fff3c4" | The following applications can be used to handle { $description } links.
|-
| 159 || — || style="background:#fff3c4" | Show a reminder for missing attachments if the email contains matching keywords. || ''same as 159''
|-
| 159 || Example: .mozilla.org, .net.nz, 192.168.1.0/24 || style="background:#fff3c4" | '''Examples:''' .mozilla.org, .net.nz, 192.168.1.0/24 || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Main font style: || ''same as 159''
|-
| 159 || Sans-serif: || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Character set: || ''same as 159''
|-
| 159 || Fonts for: || style="background:#fff3c4" | — || —
|-
| 159 || Proportional: || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Sans-serif font: || ''same as 159''
|-
| 159 || Yes || style="background:#fff3c4" | — || —
|-
| 159 || No || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Send messages waiting in your Outbox || ''same as 159''
|-
| 159 || Offline || style="background:#fff3c4" | — || —
|-
| 159 || Online || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Add file type to attached messages || ''same as 159''
|-
| 159 || Show an alert || style="background:#fff3c4" | — || —
|-
| 159 || Cards view || style="background:#fff3c4" | — || —
|-
| 159 || View Style: || style="background:#fff3c4" | — || —
|-
| 159 || Keywords… || style="background:#fff3c4" | — || —
|-
| 159 || Bold Italic || style="background:#fff3c4" | Bold '''italic''' || ''same as 159''
|-
| 159 || Cards View Options || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | App badges and notifications || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Always check to see if Thunderbird is the default email app when opened || ''same as 159''
|-
| 159 || Choose… || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | When Thunderbird is closed, move it to the tray || ''same as 159''
|-
| 159 || Allow Thunderbird to send backlogged crash reports on your behalf || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Data sharing is turned off. Past usage data will be permanently deleted from { -vendor-short-name } servers within 30 days. || ''same as 159''
|-
| 159 || You’re no longer allowing { -vendor-short-name } to capture technical and interaction data. All past data will be deleted within 30 days. || style="background:#fff3c4" | — || —
|-
| 159 || Allow Thunderbird to send technical and interaction data to { -vendor-short-name } || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Data collected to improve Thunderbird || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Send anonymous crash reports to { -vendor-short-name } || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | (Includes basic technical info like your operating system, memory usage, and feature activity. Thunderbird never collects email content, contacts, or personal messages.) || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Share anonymous performance data with { -vendor-short-name } || ''same as 159''
|-
| 159 || Automatic || style="background:#fff3c4" | — || —
|-
| 159 || Addressing || style="background:#fff3c4" | — || —
|-
| 159 || Customize… || style="background:#fff3c4" | — || —
|-
| 159 || Ascending || style="background:#fff3c4" | — || —
|-
| 159 || Descending || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Only show display name for contacts saved in the address book || ''same as 159''
|-
| 159 || Advanced… || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Email notifications || ''same as 159''
|-
| 159 || Indexing || style="background:#fff3c4" | — || —
|-
| 159 || Inline || style="background:#fff3c4" | — || —
|-
| 159 || Language || style="background:#fff3c4" | — || —
|-
| 159 || Mail Content || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Select audio… || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | After viewing for || ''same as 159''
|-
| 159 || When Thunderbird is minimized, move it to the tray || style="background:#fff3c4" | — || —
|-
| 159 || Settings… || style="background:#fff3c4" | — || —
|-
| 159 || Default Protection || style="background:#fff3c4" | — || —
|-
| 159 || Certificates || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Note: Accounts that use web sign-in (like Gmail or Yahoo), require authentication again on your device. || ''same as 159''
|-
| 159 || When manually marked as spam || style="background:#fff3c4" | — || —
|-
| 159 || — || style="background:#fff3c4" | Check spelling while typing || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Start Thunderbird in the tray || ''same as 159''
|-
| 159 || — || style="background:#fff3c4" | Underline text links in messages || ''same as 159''
|-
| 159 || MB of space for the cache || style="background:#fff3c4" | — || —
|}

User:SpikeUK1

SpikeUK1 — Sat, 31 Oct 2026 10:01:08 GMT

Account approvals : October 2026: Six likely spammer/s rejected. Backlog zero.

← Older revision		Revision as of 10:01, 31 October 2026
Line 233:		Line 233:
	\|-		\|-
	\| 30<sup>th</sup> October 2026 \|\| 0 \|\| 1 \|\| 0 \|\| 0 \|\| 1		\| 30<sup>th</sup> October 2026 \|\| 0 \|\| 1 \|\| 0 \|\| 0 \|\| 1
			\|-
			\| 31<sup>st</sup> October 2026 \|\| 0 \|\| 6 \|\| 0 \|\| 0 \|\| 6
	\|}		\|}

User:Mstanke

Mstanke — Fri, 30 Oct 2026 20:12:08 GMT

Blanked the page

← Older revision		Revision as of 20:12, 30 October 2026
Line 1:		Line 1:
	~~https://people.mozilla.org/p/mstanke~~

User:SpikeUK1

SpikeUK1 — Fri, 30 Oct 2026 09:24:03 GMT

Account approvals : October 2026: One likely spammer rejected. Backlog zero.

← Older revision		Revision as of 09:24, 30 October 2026
Line 231:		Line 231:
	\|-		\|-
	\| 29<sup>th</sup> October 2026 \|\| 0 \|\| 12 \|\| 0 \|\| 0 \|\| 12		\| 29<sup>th</sup> October 2026 \|\| 0 \|\| 12 \|\| 0 \|\| 0 \|\| 12
			\|-
			\| 30<sup>th</sup> October 2026 \|\| 0 \|\| 1 \|\| 0 \|\| 0 \|\| 1
	\|}		\|}

Support:Releases

Alice Wyman — Thu, 29 Oct 2026 21:15:35 GMT

2026 releases: Firefox 159 (current)

← Older revision		Revision as of 21:15, 29 October 2026
Line 19:		Line 19:
	\|[https://wiki.mozilla.org/Support/Firefox160 Firefox 160]		\|[https://wiki.mozilla.org/Support/Firefox160 Firefox 160]
	\|-		\|-
	\|[https://wiki.mozilla.org/Support/Firefox159 Firefox 159]		\|'''[https://wiki.mozilla.org/Support/Firefox159 Firefox 159]''' (current)
	\|-		\|-
	\|~~'''~~[https://wiki.mozilla.org/Support/Firefox158 Firefox 158]~~''' (current)~~		\|[https://wiki.mozilla.org/Support/Firefox158 Firefox 158]
	\|-		\|-
	\|[https://wiki.mozilla.org/Support/Firefox157 Firefox 157]		\|[https://wiki.mozilla.org/Support/Firefox157 Firefox 157]

Privacy/Docs/How To Triage ETP-Strict Website Breakage

Manuel Bucher — Thu, 29 Oct 2026 21:08:27 GMT

Triage Quick Links: Add "Ready but bot won't pick up" query

← Older revision		Revision as of 21:08, 29 October 2026
Line 22:		Line 22:
	* [https://bugzilla.mozilla.org/buglist.cgi?query_based_on=Needs+allow+list+category&product=Web+Compatibility&component=Privacy%3A+Site+Reports&resolution=---&query_format=advanced&f1=status_whiteboard&o1=notsubstring&v1=%5Bexception-&f2=cf_user_story&o2=substring&v2=trackers-&f3=status_whiteboard&o3=substring&v3=%5Bprivacy-team%3Adiagnosed%5D Needs allow list category] (Assign categories following [https://docs.google.com/document/d/15Nw7OAMzsHxR4hPu5ZQ117w-KrDVZd3ZE-ISQ5tdSOE/edit ETP Exception Classification Criteria])		* [https://bugzilla.mozilla.org/buglist.cgi?query_based_on=Needs+allow+list+category&product=Web+Compatibility&component=Privacy%3A+Site+Reports&resolution=---&query_format=advanced&f1=status_whiteboard&o1=notsubstring&v1=%5Bexception-&f2=cf_user_story&o2=substring&v2=trackers-&f3=status_whiteboard&o3=substring&v3=%5Bprivacy-team%3Adiagnosed%5D Needs allow list category] (Assign categories following [https://docs.google.com/document/d/15Nw7OAMzsHxR4hPu5ZQ117w-KrDVZd3ZE-ISQ5tdSOE/edit ETP Exception Classification Criteria])
	* [https://bugzilla.mozilla.org/buglist.cgi?query_based_on=Ready+to+be+added+to+RemoteSettings&product=Web+Compatibility&component=Privacy%3A+Site+Reports&resolution=---&bug_status=ASSIGNED&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=REOPENED&query_format=advanced&f1=status_whiteboard&o1=substring&v1=%5Bexception-&f2=cf_user_story&o2=substring&v2=trackers-blocked%3A&f3=status_whiteboard&o3=substring&v3=%5Bprivacy-team%3Adiagnosed%5D Ready to be added to RemoteSettings] (To be picked up by the bot)		* [https://bugzilla.mozilla.org/buglist.cgi?query_based_on=Ready+to+be+added+to+RemoteSettings&product=Web+Compatibility&component=Privacy%3A+Site+Reports&resolution=---&bug_status=ASSIGNED&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=REOPENED&query_format=advanced&f1=status_whiteboard&o1=substring&v1=%5Bexception-&f2=cf_user_story&o2=substring&v2=trackers-blocked%3A&f3=status_whiteboard&o3=substring&v3=%5Bprivacy-team%3Adiagnosed%5D Ready to be added to RemoteSettings] (To be picked up by the bot)
			* [https://bugzilla.mozilla.org/buglist.cgi?query_based_on=Ready+but+bot+wont+pick+up&product=Web+Compatibility&component=Privacy%3A+Site+Reports&resolution=---&n1=1&n2=1&n3=1&status_whiteboard=%5Bprivacy-team%3Adiagnosed%5D&status_whiteboard_type=substring&query_format=advanced&j_top=OR&f1=cf_user_story&o1=substring&v1=trackers-blocked%3A&f2=cf_user_story&o2=substring&v2=classifier-features%3A&f3=OP&j3=OR&f4=status_whiteboard&o4=casesubstring&v4=%5Bexception-baseline%5D&f5=status_whiteboard&o5=casesubstring&v5=%5Bexception-convenience%5D&f6=CP Ready but bot won't pick up]

	== Identifying blocked URLs ==		== Identifying blocked URLs ==

Media/WebRTC/libwebrtc Update Process

Bcampen — Thu, 29 Oct 2026 16:18:54 GMT

ws fixup

← Older revision		Revision as of 16:18, 29 October 2026
(One intermediate revision by the same user not shown)
Line 42:		Line 42:
	)		)

	* ~~bootstrap and~~ sanity build		* sanity build (mach bootstrap is no longer supported on mercurial checkouts)
	~~./mach --no-interactive bootstrap --application-choice=browser &&~~ ./mach build		./mach build

	* Run loop-ff.sh		* Run loop-ff.sh

Firefox/Channels/Meetings/2026-10-29

Dmeehan — Thu, 29 Oct 2026 14:37:27 GMT

New page

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Thursdays at 7:30am Pacific Time
* Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings

'''Video/Teleconference Details'''
* Zoom Meeting ID: 536 097 768
* https://mozilla.zoom.us/j/536097768

{{Notes}}

__FORCETOC__

== Attendees ==
dmeehan, RyanVM, dsmith, dbodea, apetridean, tzsoldos, mboldan,

== Schedule Update ==
* 159
** Desktop 159.0 and Android Fenix/Focus 159.0 live @ 100% rollout
** Desktop and Android planned dot release scheduled for next week
*** gtb on 2026-11-02, go-live on 2026-11-03 after QA sign-off
** Firefox iOS 159.1 scheduled to start phased rollout at 03:00 UTC on 2026-11-01
* 160
** Desktop/Android 160.0b2 live @ 100%
** Desktop 160.0b3 gtb tomorrow @ 100% rollout
** Android 160.0b3 gtb tomorrow @ 99% rollout
*** Bumping to 100% pending QA sign-off
** The deadline for Release Notes is 2026-11-05
** Desktop/Android 160 Release Candidate builds on Nov 5, 2026
** Firefox iOS 160.0 branches and Firefox iOS 160.0 gtb tomorrow
* 161
** New cycle has started for Fx161
** Merge Day and 161.0b1 build1 gtb 2026-11-05

== Release Quality Metrics ==
* https://bugdash.moz.tools/#tab.beta

== Desktop Stability ==
=== Nightly ===
crash incidence (% of users experiencing a crash): 1.74% (-0.04pp compared to previous week)
* high frequency Crash in [@ mozilla::layers::VideoBridgeChild::Open]
** https://bugzilla.mozilla.org/show_bug.cgi?id=2086368
** has assignee

=== Beta ===
crash incidence: 2.17% (+0.10pp)

=== Release ===
crash incidence: 1.06% (-0.03pp)

== Mobile Stability ==
=== Nightly ===
* Crash in [@ mozilla::layers::LayerTreeOwnerTracker::Map]
** https://bugzilla.mozilla.org/show_bug.cgi?id=2086361
** developer needinfoed

== QA ==
=== Nightly ===
* Recurring testing
** Nightly 161 WebRTC testing started today.
* New feature testing in progress.
** Nightly 161 new feature testing started today.
=== Aurora / Dev Edition ===
=== Beta ===
* Recurring testing
** Beta 160 top sites web compat testing - completed.
* New feature testing
** Uplift verification for Beta 160 new features is in progress.
=== Mobile ===
* Android
** Build Signoffs Fenix & Focus
*** Beta 161.0b1 build 1 - sign-off status GREEN
*** Beta 161.0b1 build 2 - sign-off status GREEN
** Feature Testing
*** [QA-5817] Android - Listen to Page - Nightly 160 – status Yellow
*** [QA-5870] Make All wallpapers edge to edge - Nightly 160 – status Yellow
*** [QA–5922] Weekly Privacy Report Notifications- Nightly 161 – testing in progress
*** [QA-5935] Scrollable screenshots - Beta 160 - testing in progress
*** [QA-5899] [Fenix] Collections to Tab Groups migration - Beta 160 - testing in progress
*** [QA-5755] Android - investigate sync and accounts and find bugs - exploratory in progress

* iOS
** Build Signoffs
*** Firefox iOS 159.1 (79158) - Release Candidate 1- status [GREEN]
** Feature Testing
*** [QA-5561] - iOS - Continuous Onboarding - nightly testing in progress

== Action items ==

== Roundtable & Special Topics ==

[[category:Channel_Meetings|{{SUBPAGENAME}}]]
[[Category:Wikipage templates]]

User:SpikeUK1

SpikeUK1 — Thu, 29 Oct 2026 13:02:31 GMT

Account approvals : October 2026: Twelve likely spammer/s rejected. Backlog zero.

← Older revision		Revision as of 13:02, 29 October 2026
Line 229:		Line 229:
	\|-		\|-
	\| 28<sup>th</sup> October 2026 \|\| 0 \|\| 8 \|\| 0 \|\| 0 \|\| 8		\| 28<sup>th</sup> October 2026 \|\| 0 \|\| 8 \|\| 0 \|\| 0 \|\| 8
			\|-
			\| 29<sup>th</sup> October 2026 \|\| 0 \|\| 12 \|\| 0 \|\| 0 \|\| 12
	\|}		\|}

BMO/Recent Changes/2026-10

DaveLawrence — Wed, 28 Oct 2026 21:13:27 GMT

← Older revision		Revision as of 21:13, 28 October 2026
Line 1:		Line 1:
			== 2026-10-28 ==

			[https://github.com/mozilla-bteam/bmo/tree/release-20261028.1 release-20261028.1]
			* {{bug\|2081856}} Migrate Bug REST resource to native Mojo API: attachments (attachments, add_attachment, update_attachment)
			* {{bug\|2080901}} [BMO-ETL] When any table fails to export, the entire snapshot should be rolled back to avoid incorrect results in charts/dashboards
			* {{bug\|2085028}} log_user_request logs empty request_url/user_agent and server "web" for native Mojo API routes
			* {{bug\|2067852}} Migrate rst docs to markdown and host inside of bugzilla itself
			* {{bug\|2085553}} Github logins are failing with JSON error after recent changes to Bugzilla
			* {{bug\|2078938}} Message/Banner for people creating tickets under mozilla.org :: GitHub: Administration
			* {{bug\|2064523}} [meta] tracking bug for BMO dependency upgrades
			* {{bug\|2086615}} Change the ability to see groups a user is a member of via /rest/user?names=<name> to the group can_see_groups
			* {{bug\|1883428}} Improve the needinfo email situation (use HTML, drop unnecessary emails)
			* {{bug\|2084154}}

	== 2026-10-21 ==		== 2026-10-21 ==

BMO/Recent Changes

DaveLawrence — Wed, 28 Oct 2026 21:13:04 GMT

@@ Line 1: / Line 1: @@
 = Recent Changes =
 == 2026-10-21 ==
@@ Line 32: / Line 46: @@
 * {{bug|1273193}} Get Comments webservice docs don’t mention author
 * {{bug|2078352}} Selenium test 4_test_votes.t fails with Firefox ESR 153 because go_to_bug doesn't wait for the module expand animation
 = Archive =

Support/Firefox159

Kelimutu — Wed, 28 Oct 2026 18:52:03 GMT

Disclaimer: URL update missing

← Older revision		Revision as of 18:52, 28 October 2026
(One intermediate revision by the same user not shown)
Line 5:		Line 5:
	== Disclaimer ==		== Disclaimer ==
	The following information is intended for members of the Mozilla Support community for the purpose of supporting users in the Mozilla Support platform. Mozilla Support is a community of enthusiastic volunteers and employees trying to support Mozilla's users around the globe. You can join us by contributing through the following ways:		The following information is intended for members of the Mozilla Support community for the purpose of supporting users in the Mozilla Support platform. Mozilla Support is a community of enthusiastic volunteers and employees trying to support Mozilla's users around the globe. You can join us by contributing through the following ways:
	* [https://~~support~~.~~mozilla.org~~/~~contribute/forum~~ Answer questions in the support forum]		* [https://mzl.la/4eToqY7 Answer questions in the support forum]
	* [https://~~support.mozilla~~.~~org~~/~~contribute/kb~~ Write help articles]		* [https://mzl.la/4zhqYrt Write help articles]
	* [https://~~support~~.~~mozilla.org/contribute~~/~~l10n~~ Localize support content]		* [https://mzl.la/4icB5Yp Localize support content]

	{{admon/note\|To learn more about how to stay updated with Firefox release information, trending, and known issues, please also check out [https://support.mozilla.org/en-US/kb/stay-updated-firefox-releases How to stay updated with Firefox release]}}		{{admon/note\|To learn more about how to stay updated with Firefox release information, trending, and known issues, please also check out [https://support.mozilla.org/en-US/kb/stay-updated-firefox-releases How to stay updated with Firefox release]}}

	== Release notes ==		== Release notes ==
	* [https://~~www~~.~~firefox.com/firefox/159.0/releasenotes~~/ Desktop 159.0 Release Notes]		* [https://mzl.la/3WAF4pc Desktop 159.0 Release Notes]
	* [https://~~www.firefox~~.~~com/firefox/153.6.0/releasenotes~~/ ESR 153.6.0 Release Notes]		* [https://mzl.la/4yRunwa ESR 153.6.0 Release Notes]
	* [https://~~www~~.~~firefox.com/firefox/115.44.0/releasenotes~~/ ESR 115.44.0 Release Notes]		* [https://mzl.la/4zTJAO0 ESR 115.44.0 Release Notes]
	* [https://~~firefox-admin-docs.mozilla~~.~~org/release-notes/version/firefox-159~~/ Firefox 159 release notes for enterprise admins] (Firefox administrator reference)		* [https://mzl.la/4yS49JZ Firefox 159 release notes for enterprise admins] (Firefox administrator reference)
	* [https://~~www~~.~~firefox.com/firefox/enterprise/159.0/releasenotes~~/ Firefox Enterprise 159.0 Release Notes]		* [https://mzl.la/4zRbN8e Firefox Enterprise 159.0 Release Notes]
	* [https://~~developer.mozilla~~.~~org/docs/Mozilla/Firefox/Releases~~/~~159~~ Firefox for developers 159 Release Notes]		* [https://mzl.la/3WBQ9GB Firefox for developers 159 Release Notes]
	* [https://~~www.firefox.com/en-US/firefox/android/159~~.~~0/releasenotes~~/ Firefox for Android 159.0 Release Notes]		* [https://mzl.la/4BtKzGg Firefox for Android 159.0 Release Notes]
	* [https://~~www.firefox.com/firefox/ios/159~~.~~0/releasenotes~~/ Firefox for iOS 159.0 Release Notes]		* [https://mzl.la/4jFJa9c Firefox for iOS 159.0 Release Notes]

	== Dot releases ==		== Dot releases ==
Line 38:		Line 38:
	== Contributor discussions ==		== Contributor discussions ==
	Please refer to the following contributor forum threads to learn more about known issues and discuss with other contributors:		Please refer to the following contributor forum threads to learn more about known issues and discuss with other contributors:
	* [https://~~support~~.~~mozilla.org/forums/contributors~~/~~717776~~ Desktop release discussion]		* [https://mzl.la/4sAse6A Desktop release discussion]
	* [https://~~support.mozilla~~.~~org/forums/contributors~~/~~717774~~ Mobile release discussion]		* [https://mzl.la/48jCs1z Mobile release discussion]
	* [https://~~support.mozilla~~.~~org/forums~~/~~l10n-forum~~ Localization discussion]		* [https://mzl.la/4yO0MU6 Localization discussion]

	You can also join our [https://~~chat~~.~~mozilla.org/#/room~~/~~#SUMO:mozilla.org~~ Matrix channel] to ask questions/join community discussion.		You can also join our [https://mzl.la/4zZCg3s Matrix channel] to ask questions/join community discussion.

	== Stay updated ==		== Stay updated ==
	Apart from sharing release information, there are other ways to stay updated with product release and community updates:		Apart from sharing release information, there are other ways to stay updated with product release and community updates:
	* '''Community call:''' We run a monthly community call (usually on the same week we release a new Firefox version). Check our schedule [https://~~wiki~~.~~mozilla.org~~/~~Support:Community_Calls~~ here] and don't hesitate to join the call in person if you can!		* '''Community call:''' We run a monthly community call (usually on the same week we release a new Firefox version). Check our schedule [https://mzl.la/3UQc3p6 here] and don't hesitate to join the call in person if you can!
	* '''Newsletter:''' Consider subscribing to [https://mzl.la/3NZO8tI Firefox Daily Digest] to get daily updates (Mon-Fri) about Firefox from across the internet.		* '''Newsletter:''' Consider subscribing to [https://mzl.la/3NZO8tI Firefox Daily Digest] to get daily updates (Mon-Fri) about Firefox from across the internet.

Line 62:		Line 62:
	\|-		\|-
	\|'''Content request:'''		\|'''Content request:'''
	\|colspan="2"\|[https://~~bugzilla~~.~~mozilla.org~~/~~show_bug.cgi?id=~~2069171]		\|colspan="2"\|[https://mzl.la/4zXiKV8 bug 2069171]
	\|-		\|-
	\|'''KB article:'''		\|'''KB article:'''
	\|[https://~~support~~.~~mozilla.org/en-US/kb~~/~~closed-browser-notifications~~] [https://~~support.mozilla~~.~~org/en-US/kb~~/~~push-notifications-firefox~~]		\|[https://mzl.la/4e4wpkU] [https://mzl.la/4zqU2MY]
	\|New article, updated article		\|New article, updated article
	\|}		\|}
Line 168:		Line 168:

	== Product discussions on Mozilla Connect ==		== Product discussions on Mozilla Connect ==
	Check out top voted requests on [https://~~connect~~.~~mozilla.org~~/ Mozilla Connect].		Check out top voted requests on [https://mzl.la/4knkTF3 Mozilla Connect].
	<!--		<!--
	{\| class="wikitable"		{\| class="wikitable"

User:SpikeUK1

SpikeUK1 — Wed, 28 Oct 2026 14:31:29 GMT

Account approvals : October 2026: One more likely spammer rejected. Backlog zero.

← Older revision		Revision as of 14:31, 28 October 2026
Line 228:		Line 228:
	\| 27<sup>th</sup> October 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7		\| 27<sup>th</sup> October 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7
	\|-		\|-
	\| 28<sup>th</sup> October 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7		\| 28<sup>th</sup> October 2026 \|\| 0 \|\| 8 \|\| 0 \|\| 0 \|\| 8
	\|}		\|}

WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 22

Whimboo — Wed, 28 Oct 2026 13:04:41 GMT

Created page with "= WebDriver BiDi Milestone 22 - In Development = '''Goal''': TODO '''Progress''': * [https://docs.google.com/spreadsheets/d/1---9z3XNVd08fax44coEpa3ikmK1fdqQb8zBzEibxRE Tracking spreadsheet] '''Queries''': * [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&resolution=FIXED&query_format=advanced&o1=substring&v1=%5Bwebdriver%3Am22 Completed Bugs] '''Milestone Backlog''': <bugzilla> { "whiteboard": "[webdriver:m22", "include_fields":"id, sum..."

New page

= WebDriver BiDi Milestone 22 - In Development =
'''Goal''': TODO

'''Progress''':
* [https://docs.google.com/spreadsheets/d/1---9z3XNVd08fax44coEpa3ikmK1fdqQb8zBzEibxRE Tracking spreadsheet]

'''Queries''':
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&resolution=FIXED&query_format=advanced&o1=substring&v1=%5Bwebdriver%3Am22 Completed Bugs]

'''Milestone Backlog''':
<bugzilla>
{
"whiteboard": "[webdriver:m22",
"include_fields":"id, summary, priority, cf_fx_points, status, assigned_to"
}
</bugzilla>

WebDriver/RemoteProtocol/WebDriver BiDi

Whimboo — Wed, 28 Oct 2026 13:01:01 GMT

Placeholder for M22

← Older revision		Revision as of 13:01, 28 October 2026
Line 6:		Line 6:
	== Milestones ==		== Milestones ==

	=== WebDriver BiDi Milestone 22 - Completed September 27th, 2026 ===		=== WebDriver BiDi Milestone 22 - In Development ===
			'''Goal''': TODO

			'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_22\|Milestone 22 status]]


			=== WebDriver BiDi Milestone 21 - Completed September 27th, 2026 ===
	'''Goal''': This milestone, we will continue working on streaming support (screencasting, network responses, etc.) and WebSocket events, and improve worker support across different commands and events. We will also focus on improving protocol security, and aim to enable widget-level touch event support for web-platform tests. As always we plan to work on a number of smaller items, that are important for the clients like improving console logging and download events, adding element scrolling action and more.		'''Goal''': This milestone, we will continue working on streaming support (screencasting, network responses, etc.) and WebSocket events, and improve worker support across different commands and events. We will also focus on improving protocol security, and aim to enable widget-level touch event support for web-platform tests. As always we plan to work on a number of smaller items, that are important for the clients like improving console logging and download events, adding element scrolling action and more.

User:SpikeUK1

SpikeUK1 — Wed, 28 Oct 2026 09:12:15 GMT

Account approvals : October 2026: Seven likely spammer/s rejected. Backlog zero.

← Older revision		Revision as of 09:12, 28 October 2026
Line 227:		Line 227:
	\|-		\|-
	\| 27<sup>th</sup> October 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7		\| 27<sup>th</sup> October 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7
			\|-
			\| 28<sup>th</sup> October 2026 \|\| 0 \|\| 7 \|\| 0 \|\| 0 \|\| 7
	\|}		\|}

Support/Firefox159

Alice Wyman — Tue, 27 Oct 2026 23:12:11 GMT

Firefox Desktop content update: updated article

← Older revision		Revision as of 23:12, 27 October 2026
(2 intermediate revisions by the same user not shown)
Line 13:		Line 13:
	== Release notes ==		== Release notes ==
	* [https://www.firefox.com/firefox/159.0/releasenotes/ Desktop 159.0 Release Notes]		* [https://www.firefox.com/firefox/159.0/releasenotes/ Desktop 159.0 Release Notes]
	* [https://www.firefox.com/firefox/153.5.0/releasenotes/ ESR 153.5.0 Release Notes]		* [https://www.firefox.com/firefox/153.6.0/releasenotes/ ESR 153.6.0 Release Notes]
	* [https://www.firefox.com/firefox/115.43.0/releasenotes/ ESR 115.43.0 Release Notes]		* [https://www.firefox.com/firefox/115.44.0/releasenotes/ ESR 115.44.0 Release Notes]
	* [https://firefox-admin-docs.mozilla.org/release-notes/version/firefox-~~158~~/ Firefox for Enterprise ~~158~~ Release Notes]		* [https://firefox-admin-docs.mozilla.org/release-notes/version/firefox-159/ Firefox 159 release notes for enterprise admins] (Firefox administrator reference)
	* [https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/~~158~~ Firefox for developers ~~158~~ Release Notes]		* [https://www.firefox.com/firefox/enterprise/159.0/releasenotes/ Firefox Enterprise 159.0 Release Notes]
	* [https://www.firefox.com/firefox/android/~~158~~.0/releasenotes/ Firefox for Android ~~158~~.0 Release Notes]		* [https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/159 Firefox for developers 159 Release Notes]
	* [https://www.firefox.com/firefox/ios/~~158~~.0/releasenotes/ Firefox for iOS ~~158~~.0 Release Notes]		* [https://www.firefox.com/en-US/firefox/android/159.0/releasenotes/ Firefox for Android 159.0 Release Notes]
			* [https://www.firefox.com/firefox/ios/159.0/releasenotes/ Firefox for iOS 159.0 Release Notes]

	== Dot releases ==		== Dot releases ==
Line 48:		Line 49:
	* '''Newsletter:''' Consider subscribing to [https://mzl.la/3NZO8tI Firefox Daily Digest] to get daily updates (Mon-Fri) about Firefox from across the internet.		* '''Newsletter:''' Consider subscribing to [https://mzl.la/3NZO8tI Firefox Daily Digest] to get daily updates (Mon-Fri) about Firefox from across the internet.

	== What's new in Firefox ~~158~~ ==		== What's new in Firefox 159 ==

	{{admon/note\|Content in this page is being updated periodically as we're rolling out the release.}}		{{admon/note\|Content in this page is being updated periodically as we're rolling out the release.}}

	=== Firefox Desktop content update ===		=== Firefox Desktop content update ===

	{\| class="wikitable"		{\| class="wikitable"
	!colspan="3"\|Closed-browser web notifications		!colspan="3"\|Closed-browser web notifications
Line 63:		Line 65:
	\|-		\|-
	\|'''KB article:'''		\|'''KB article:'''
	\|[https://support.mozilla.org/en-US/kb/closed-browser-notifications]		\|[https://support.mozilla.org/en-US/kb/closed-browser-notifications] [https://support.mozilla.org/en-US/kb/push-notifications-firefox]
	\|New article		\|New article, updated article
	\|}		\|}
	<!--		<!--
Line 119:		Line 121:
	\|Article link		\|Article link
	\|}		\|}

	~~-->~~

	=== Firefox for Android content update ===		=== Firefox for Android content update ===

User:Tlin/2026

Tlin — Tue, 27 Oct 2026 21:48:24 GMT

Created page with "= 2026 Bug Summary = == 2026 H1 == === Bug Resolved === <bugzilla> { "changed_after": "2026-01-01", "changed_before": "2026-06-30", "assigned_to": ["aethanyc@gmail.com"], "include_fields": "id, product, component, summary, status, resolution, assigned_to", "changed_field": "status", "changed_field_to": "resolved" } </bugzilla> === Bug Reported === <bugzilla> { "changed_after": "2026-01-01", "changed_before": "2026-06-30", "reporter": ["aethanyc@gmail.co..."

New page

= 2026 Bug Summary =
== 2026 H1 ==
=== Bug Resolved ===
<bugzilla>
{
"changed_after": "2026-01-01",
"changed_before": "2026-06-30",
"assigned_to": ["aethanyc@gmail.com"],
"include_fields": "id, product, component, summary, status, resolution, assigned_to",
"changed_field": "status",
"changed_field_to": "resolved"
}
</bugzilla>
=== Bug Reported ===
<bugzilla>
{
"changed_after": "2026-01-01",
"changed_before": "2026-06-30",
"reporter": ["aethanyc@gmail.com"],
"changed_field": "creation_time",
"include_fields": "id, product, component, summary, status, resolution, assigned_to"
}
</bugzilla>

== 2026 H2 ==
=== Bug Resolved ===
<bugzilla>
{
"changed_after": "2026-07-01",
"changed_before": "2026-12-31",
"assigned_to": ["aethanyc@gmail.com"],
"include_fields": "id, product, component, summary, status, resolution, assigned_to",
"changed_field": "status",
"changed_field_to": "resolved"
}
</bugzilla>
=== Bug Reported ===
<bugzilla>
{
"changed_after": "2026-07-01",
"changed_before": "2026-12-31",
"reporter": ["aethanyc@gmail.com"],
"changed_field": "creation_time",
"include_fields": "id, product, component, summary, status, resolution, assigned_to"
}
</bugzilla>

← Older revision		Revision as of 16:50, 2 November 2026
Line 169:		Line 169:
	*University of Cape Town \| Cape Town \| Malebogo Ngoepe		*University of Cape Town \| Cape Town \| Malebogo Ngoepe
	*University of Witwatersrand \| Johannesburg \| Richard Klein		*University of Witwatersrand \| Johannesburg \| Richard Klein
	*University of the Western Cape \| Cape Town \| ~~Mmaki Jantjies~~		*University of the Western Cape \| Cape Town \| Carolien van den Berg
	*Central University of Technology, Free State \| Bloemfontein \| Luzaan Schlebusch		*Central University of Technology, Free State \| Bloemfontein \| Luzaan Schlebusch
	*University of Pretoria \| Pretoria \| Marlene Holmner		*University of Pretoria \| Pretoria \| Marlene Holmner

← Older revision		Revision as of 21:13, 28 October 2026
Line 1:		Line 1:
			== 2026-10-28 ==

			[https://github.com/mozilla-bteam/bmo/tree/release-20261028.1 release-20261028.1]
			* {{bug\|2081856}} Migrate Bug REST resource to native Mojo API: attachments (attachments, add_attachment, update_attachment)
			* {{bug\|2080901}} [BMO-ETL] When any table fails to export, the entire snapshot should be rolled back to avoid incorrect results in charts/dashboards
			* {{bug\|2085028}} log_user_request logs empty request_url/user_agent and server "web" for native Mojo API routes
			* {{bug\|2067852}} Migrate rst docs to markdown and host inside of bugzilla itself
			* {{bug\|2085553}} Github logins are failing with JSON error after recent changes to Bugzilla
			* {{bug\|2078938}} Message/Banner for people creating tickets under mozilla.org :: GitHub: Administration
			* {{bug\|2064523}} [meta] tracking bug for BMO dependency upgrades
			* {{bug\|2086615}} Change the ability to see groups a user is a member of via /rest/user?names=<name> to the group can_see_groups
			* {{bug\|1883428}} Improve the needinfo email situation (use HTML, drop unnecessary emails)
			* {{bug\|2084154}}

	== 2026-10-21 ==		== 2026-10-21 ==