Overall beta scope is not every feature’s scope
The France/French beta expansion and the English US/Canada form-and-watch launch have different boundaries. Do not transfer one announcement’s eligibility to another feature.
LUMACTA NEWS / DATED STORY TRACKER
Follow the dated record behind Firefox’s AI controls and Smart Window. This dossier connects plans, release records and limited beta changes, then keeps current documentation gaps separate from events that actually happened.
Evidence checked .
The France/French beta expansion and the English US/Canada form-and-watch launch have different boundaries. Do not transfer one announcement’s eligibility to another feature.
Firefox 148’s release record establishes the desktop AI Controls milestone. It does not establish access to every separately offered AI capability.
Current help assigns form processing to Gemini 3.1 Flash Lite and tasks to Qwen. A chosen chat model should not be assumed to govern both operations.
Mozilla says page monitoring runs while Firefox is open. This record does not establish an independent, always-running alert service.
The setup help describes an optional desktop window requiring a Mozilla account. Check account, version, country and feature conditions separately.
Most recent event first. Event dates and source-publication dates are kept separate from the evidence-check time above.
Showing all 8 dated timeline events.
No dated events match this filter. The current record, open questions and full source list remain available.
Mozilla announced form suggestions from selected tabs and scheduled page watches for desktop Smart Window beta in English in the United States and Canada. Firefox 159’s release notes list page watching as a progressive rollout.
Mozilla announced Mistral Small 4 for Smart Window and expansion of the overall beta to France with French-language support. Its updated August article separately described the French rollout beginning on September 16.
In its August beta update, Mozilla described Exa-supported web retrieval with sources, suggested tab groups, duplicate-tab closure by a click and visual history previews. These are issuer-described capabilities, not Lumacta test results.
Primary evidence [6]
Mozilla’s June roadmap said people could try Smart Window without joining a waitlist. It did not establish the first beta date, a finished product, or access in every country.
Primary evidence [5]
Mozilla extended AI controls to Firefox on iOS and Android, with available options depending on device and location. This is a mobile-controls milestone, separate from the desktop Smart Window beta.
Primary evidence [4]
Firefox 148’s release record lists the new AI Controls section in Settings. The dated release supports a shipped-browser milestone; the availability of every separate AI feature still has its own conditions.
Primary evidence [3]
Mozilla announced a central AI-controls setting for desktop Firefox 148, scheduled for February 24. It described a global switch for Firefox’s AI enhancements and separate choices for individual browser features.
Primary evidence [2]
Mozilla introduced an optional AI Window concept and invited people to register for updates and early feedback. This records a development announcement, not a worldwide product release.
Primary evidence [1]
These are questions for further evidence, rather than fabricated events or promises of a future release.
Why it matters: The help instructions say four; their FAQ says five. This inconsistency prevents an exact threshold from being stated here.
Evidence needed: Consistent corrected instructions, or an explicit version-specific clarification. An observed test would also need its browser version and account scope recorded.
Why it matters: The task help measures from creation; the announcement describes 90 days without a matching change. Those rules would pause a long-running watch at different times.
Evidence needed: A consistent task-lifecycle definition covering creation, matching changes, pauses and resumption. No single expiry rule is inferred from the conflicting texts.
Why it matters: The June roadmap said no waitlist was needed, but the current setup help retains early-access waitlist language. Neither sentence proves universal current access.
Evidence needed: A current, region- and version-specific access description that reconciles the two records. The historical June statement remains dated June 16.
These links retain their original publication dates. The tracker does not turn older reporting into a new daily edition.
Source links support the stated milestones and limits. A published document, an issuer announcement, a staged rollout and a test on a reader’s own browser are different kinds of evidence.
Source published .
Source published .
Publication day not established in this record.
Source published .
Source published .
Source published .
Source published .
Source published .
Publication day not established in this record.
Publication day not established in this record.
Publication day not established in this record.
Publication day not established in this record.