De Nederlandse
Mozilla-gemeenschap

Firefox krijgt eindelijk veelgevraagde feature die Chrome en Edge al langer hadden  clickx.be

Tabs pile up fast on mobile. Imagine you’re planning a summer barbecue, and you start by searching for the best rib recipe. Twenty minutes later, you’re 17 tabs deep: comparing marinades, debating side dishes, checking the weather, making a grocery list and adding songs to a playlist.

None of those tabs are organized. They’re mixed in with everything else you’ve been browsing, making it hard to keep track of what you’re saving for later.

Now you can group related tabs in Firefox for Android, keeping them together in labeled, colored groups so you can actually find what you need when you need it.

How it works

Drag one tab onto another, or select a few and tap “Add to group.” Name it, pick a color, and you’re done.

Each group appears as a single card in the tab tray rather than a dozen separate tabs. You can open it, rename it, recolor it, or delete it whenever you want. Search still finds tabs inside a group, too.

So when you’re standing in the produce aisle looking for that rib recipe, you won’t have to scroll past dozens of unrelated tabs just to find it. Everything for your barbecue is organized together in one place, ready when you need it.

Finally sorted, as it should be

Tab grouping was the most requested feature from Firefox mobile users in 2025. And we get it: your tabs shouldn’t get harder to manage the more you use your browser. Download the latest version of Firefox for Android now to try Tab Groups, with iOS support on the way. 

The post Your Android tabs just got a lot more organized with Firefox appeared first on The Mozilla Blog.

You’re planning a trip. Reading an article. Following a recipe.

Then a question pops into your head. Sometimes it leads down a rabbit hole – with more searches, more tabs and plenty to explore. Other times, you just need a little context so you can get back to what you were doing.

That’s why we’re introducing Quick Answers for Firefox on iOS.

With Quick Answers, you can ask a question using your voice and get a concise answer. Just open a new tab, long-press the voice button and ask.

For example:

• “What does mellifluous mean?”
• “What is 95 degrees Fahrenheit in Celsius?”
• “What’s the difference between suede and nubuck?”

If a quick answer is all you need, you’re done.

If you want to dig in deeper, the links to supporting sources are there for exploration.

Built with transparency and privacy in mind

We’ve built Quick Answers to be transparent about how it works and what data is shared.

Voice is processed on your device using Apple’s speech recognition technology. No raw audio is stored or sent to the server, and Firefox doesn’t share your browsing history or personal context with the AI model. Only the transcribed text of your question is sent to generate an answer. You can turn the feature off at any time in Settings → AI Controls.

Quick Answers is starting to roll out today to Firefox for iOS users in the U.S. using English.

Oh, and if you’re wondering…

• Mellifluous means pleasant and musical to hear.
• 95 degrees Fahrenheit is 35 degrees Celsius.
• Suede is made from the underside of the hide, while nubuck is made from the outer side and buffed to create a soft, velvety texture.

Take control of your internet Download Firefox

The post Quick Answers: For the questions in between appeared first on The Mozilla Blog.

Today, we’re excited to announce the Preview of Containers in Firefox version 153, which lets you keep separate parts of your online life (work, shopping, personal, banking) logged into different accounts in the same browser window, but keeps your cookies and ad tracking isolated inside each container.

This means that stuff you do in one container isn’t seen by other containers. No longer will you search for a new hat to wear to a party, only to be inundated with ads for hats at every twist and turn on the internet for weeks to come.

For almost a decade, many of you have relied on our Multi-Account Containers extension to keep work, personal, and privacy-sensitive browsing separate without needing multiple browsers or profiles. 

We’ve heard your feedback and understood the value you find in that separation. Now, we’re bringing the power of the Multi-Account Containers extension directly into the heart of Firefox for all to benefit from.

Why bring Containers into Firefox?

Whether you’re managing multiple social media accounts, separating work projects from personal shopping, or simply keeping your banking activity distinct, Containers are designed to help you organize your digital space. By making Containers a native, first-party feature in Firefox 153, we are:

• Making it visible by default: You no longer need to hunt for an add-on to get started. Containers are built right into your browser, ready to help you manage your context from day one.
• Simplifying your workflow: We’ve focused on making it easier to open, create, and manage your containers from the places you already browse.
• Preserving what you love: For our long-time users who have relied on the add-on, the native experience is designed to maintain the core functionality, flexibility, and visual identity you depend on.
• Driving continued investment into the future of this feature, ensuring it lives on as a first party citizen of Firefox.

What to expect in the Preview

In this preview release, you can:

• Open tabs in specific containers: Keep your browsing activity isolated by context.
• Customize your workspace: Create and manage containers with your own names, colors, and icons.
• Manage settings easily: Control your container setup directly from the Firefox settings surface.
• Get Started: Right-click any tab or long-press the new tab (+) button to open a container tab — or head to Firefox Settings to create your first container.

If you’re already using the Multi-Account Containers, there’s nothing special you need to do. Not all of the features of the add-on are available in the first-party version of containers just yet, we’re still building them out.  You can continue to use the add-on alongside the built in containers, no need to uninstall the add-on.

This release represents our first step in making Firefox more adaptable to how you actually live and work online. While this is just the beginning, we have plans to refine this experience and build a foundation for future features that make context separation even more seamless.

Join the Conversation

We’re eager to hear how this native experience fits into your daily routine. As you explore the new Containers Preview in Firefox 153, please let us know what you think by posting your feedback in this Mozilla Connect thread. Your feedback helps us shape the future of these tools and ensures we’re building features that truly matter to you.

Take control of your internet Download Firefox

The post Experience Better Browsing: Introducing Native Containers in Firefox 153 appeared first on The Mozilla Blog.

Mozilla: Microsoft stuurt gebruikers nog steeds richting Edge  ictmagazine.nl

Mozilla: ‘Microsoft blijft gebruikers richting Edge sturen’  ITdaily

Chrome 150 en Firefox 152 zijn uit: kritieke lekken gedicht  Softonic.nl

Two years ago Mozilla asked two leading experts on deceptive design, Dr. Harry Brignull and Cennydd Bowles, to look at how Microsoft was treating people who tried to use a different browser on Windows. Their report, Over The Edge, documented a pattern of design choices in Windows, Edge, and Bing that nudged, pressured, and at times tricked people into using Edge.

This morning, the same researchers are publishing Over The Edge 2.0. They retested the same questions across Windows 10 and Windows 11, and added two new dimensions. First, how does Microsoft’s approach change from one jurisdiction to another? They assessed Microsoft’s tactics across four regions: the USA, India, the UK, and Germany, as a representative country in the European Economic Area. Second, they examined how AI features, specifically Copilot, are being used to shape the same outcomes the original report identified.

Their conclusion is short. Microsoft still does not allow users to download, set as the default, or keep using alternative browsers without harmful interference. The patterns are documented, and they meet established definitions of coercion, deception, and manipulation.

There is one bright spot. In Europe, where the Digital Markets Act applies, some harmful design tactics are gone. The Bing ‘All you need is right here’ panel and its trick wording. The nagging Windows 10 ‘You’re almost done setting up your PC’ journey. The Copilot data toggles that default to “On” in the US and India, by contrast default to “Off” in the EEA and the UK. Same Windows. Same Edge. Same Copilot. Different design choices, because the law required them.

That is the heart of the report. Although the EEA product still has obvious harmful design patterns, Microsoft has built a fairer user experience for browser choice. It has shipped that experience to one region. Everywhere else, including the US, the UK, India, and Brazil, harmful design patterns continue. This is an active choice – and one that can be made differently.  

The findings are the researchers’ own. Mozilla commissioned the work, and the report discloses that role, but the methodology, the screenshots, and the public journey database at edge.brignull.com let anyone check the evidence for themselves.

We make Firefox because we believe the web should serve people, not platforms. Firefox is independent, built by Mozilla, and designed around what is best for users, not what increases lock-in. 

Read the full report here.

The post Over The Edge 2.0: what independent researchers found about browser choice on Windows appeared first on The Mozilla Blog.

Open source AI has crossed a threshold. For years the debate has centered around whether open models could ever compete with closed ones. This is no longer a debate we should be having. Today Mozilla is publishing its inaugural State of Open Source AI report, built on new analysis and a global survey of 950+ developers, showing that open models are no longer playing catch-up. The performance gap with top proprietary systems like ChatGPT and Claude has narrowed to just 3%, while costs have fallen up to 50x in three years.

But the report also surfaces a harder truth. Open models now power roughly a third of real-world AI usage, but capture only 4% of the revenue. So while the value is there, it just isn’t flowing back into the open ecosystem that made it possible. Meanwhile, the geopolitical picture is shifting fast.

Asia is racing ahead

China and East Asia now lead the world in open source AI adoption, at 89%, far ahead of the West, treating open source as a cornerstone of national strategy. Governments elsewhere are responding, with 12 new national AI strategies launched last year, and 47 countries now restrict foreign processing for critical workloads. The EU, Canada, and India are backing open ecosystems with real public investment, treating AI infrastructure as a strategic asset.

Developers want open models, but they can’t always ship them.

For developers, the appetite for open source is there, and cost and privacy rank as developers’ top reasons for choosing models. But wanting to use open models and running them in production are different things. 79% of developers use open models, yet only 51% have deployed them in production, versus 63% for closed models.

As Álvaro Ruiz Cubero of SlashData, which fielded the survey for Mozilla, put it: “this gap indicates that there is not an issue purely of model quality, but of missing infrastructure. Deployment rates for open models barely increase with company size, highlighting a lack of mature tooling and support. At the same time, buyers are prioritising licensing terms (31%) and ownership (26%), signalling a clear shift toward control and flexibility over raw capability.”

The real battle has moved beyond the model

Perhaps the most important finding may be the least obvious. The layer that matters most isn’t the model. It’s the agentic harness: the software between people and models that decides what an AI system can see, remember, and do. Changing the surrounding software can affect performance more than switching the model itself. Whoever controls that layer controls how AI behaves in the world.

Right now, that layer is being built with very few guardrails. Users approve AI agent requests by default up to 93% of the time, with so-called “consent fatigue” going largely unnoticed.

“Open source AI has reached a turning point,” said Raffi Krikorian, Mozilla’s Chief Technology Officer. “It’s no longer about expanding access to models; it’s about who has the power to shape, audit, and improve them. Without investment in the infrastructure, tooling, and governance around open models, we risk locking in a system where only restrictive, closed AI can scale – and that doesn’t serve the public interest, or sovereignty over tech policy decisions.”

Be owners, not renters

Open models offer what a subscription never can: owning your infrastructure instead of renting someone else’s. Companies like Microsoft and Uber are already rethinking their reliance on paid, closed AI tools as the bills add up. The economics are shifting and so is the thinking. 

If you’re a CTO, a policymaker, a developer or an investor, this is the report for you. Read it, share it, and help build the infrastructure to make openness usable, not just possible.

Read the full Mozilla State of Open Source AI report here. 

The post Mozilla’s Inaugural ‘State of Open Source AI’ Report Is Here appeared first on The Mozilla Blog.

Firefox gaat tweewekelijks releases uitbrengen  ictmagazine.nl

Firefox krijgt dubbel zoveel nieuwe versies  Tweakers

We’ve all been there. You update a small piece of text or fix a tiny CSS bug. You push the code, and then… you wait. Your CI pipeline decides that this minor tweak means it needs to run your entire end-to-end regression suite.

It’s slow, it’s expensive, and honestly, it’s a sledgehammer to crack a nut.

If you tuned into Selenium Conference this year, you might have caught Simon Stewart’s talk. He hit on a topic that every team struggling with slow deployments needs to hear: we need to stop running things just because they are there.

Thunderbird notes 2015-12-01. NOON PT (Pacific). For meeting time, previous notes and call-in details see https://wiki.mozilla.org/Thunderbird/StatusMeetings

Attendees

• jorgk, fallen, ba, wsmwk, mkmelin,MakeMyDay, rkent, marcoagpinto, roker

MAIN FOCUS OF MEETING

• version 45
• governance, futures
• builds

Action items from last meetings

• Thunderbird Council reorganization: we’ll discuss this in the Council directly and do some reorganization. This is not a forever governance plan, but we need to be practical given the many demands of the moment.

Current status / Announcements

• Etherpads see list of names at https://public.etherpad-mozilla.org/p/thunderbird and https://public.etherpad-mozilla.org/p/calendar
• https://public.etherpad-mozilla.org/p/thunderbird38-support-issues for version 38 ESR issues
• Tree status issues: https://public.etherpad-mozilla.org/p/thunderbird-tree-status
  • Please help green up the tree – including not only c-c but also esr38, beta, and aurora
    • Please be aggressive filing bugs, and fixing what you can, so dev checkins can occur when patches become available.
    • If a bug breaks nightly or beta build or tests, please make severity=blocker
    • Please prioritize reviews/feedback requests in your queue that are tree issues!
• Thunderbird 45: string freeze 2015-12-14, interface freeze later (that’s me demanding a concession like last year).

Current Release Critical Issues

Leave critical bugs here until confirmed fixed. If confirmed, then remove.

• tracking-tb38 flags: approved(+)+unfixed in ESR: http://mzl.la/1LDrkxP nominated(?): http://tinyurl.com/pgwflyg

blocking

• 38.3.1 bug 1211160 calendar 4.0.3.1 is a workaround for 38.3.0 — Thunderbird Version 38.3 Buttons not working menu items // bug 1211291 – Folders are visible, but messages are not. (?related to bug 1211358 lightning chrome.manifest not updated in 38.3.0 ?)
• nightly (3 bugs blocking builds, all are assigned) – bug 1195442 – Mac builds broken ~1 month on nightly
• rkent is working on it – bug 1183490 – (dataloss) New emails do not adhere to sort by order received
  • Plan is to understand issues in converting completely to nextKey = ++lastKey for non-IMAP, then plan how much to implement for 38.3.0 A simple fix of the dataloss is probable. I have a try patch that does the nextKey = ++lastKey that works, now I need to think about patch for 38 (bug 1202105 needs to go to trunk and 38)
  • update 2015-10-20, patches have been posted but waiting for reviews for 2 weeks (aceman will look at those)
  • update 2015-11-17, review done 11-14, need to update and land.

important (but not top critical)

• status TBD – bug 1182629 – update to 38.1.0 from 38.0.1 re-enables disabled Lightning
• status TBD – bug 1176399 – Multiple master password when GMail OAuth2 is enabled
• status TBD – bug 1176748 – fix main thread proxies to the migration code (jorgk and m_kato have done such fixes in the past)
• filelink, proxy,
• topcrash bug 1149287 is ** 31% of our crashes** – see below

Version 45

• tracking-tb45 flags: unfixed ?/+ – http://mzl.la/1PMzNiK
• Items that may need to be checked and tested: gtk3, windows 10, windows 64bit?
• hardware acceleration – not looking promising (no changes / no testing in recent months)
• jsaccount should come in aurora

Releases

• Past
  • 38.0.1 nominally shipped 2015-06-12, 38.1.0 shipped 2015-07-10, 31.8.0 shipped 2015-07-17, 40.0beta shipped 2015-07-27 (skipping 39.0b), 38.2.0 shipped 2015-08-14, 41.0b1 2015-09-08 build2 (missed ~2015-08-10)
  • 41.0b2 (with uplifts for 38.3.0)
  • 38.3.0 ~2015-09-25 (throttled on 2015-10-06)
  • 42.0b2 2015-10-13 (42.0b1 abandoned)
  • 42.0b3 ~2015-09-23 (skipped)
  • 38.4.0 2015-11-25 (quite late) – many release notes issues
• Upcoming – https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates
  • 43.0b1 starting this week https://public.etherpad-mozilla.org/p/thunderbird-release-43b1
  • STRING FREEZE for version 45 in 2 weeks – 2015-12-14
  • 38.5.0 ~2015-12-14 ~3 weeks
  • 44.0b1 ~2015-12-14 ~3 weeks

Lightning

Past releases:

• 4.0.1.2 – bug 1182264, 4.0.2.1 – bug 1194997
• 4.0.3, 4.0.3.1 (no changes compared to 4.0.2.1)

Upcoming releases:

• 4.0.4 – bug 1215969
• 4.7.0 – bug 1225778 (TB 45)

Round Table Jorg K

• Landed six patches
  • bug 1219928 – M-C spell checker problem
  • bug 586587 + one more – M-C drag and drop onto editor window
  • ((bug|1226537}} – C-C spell check in subject problem
  • bug 1214377 – M-C editor problem, copy/paste – “white-space: pre;”
  • bug 1225864 – M-C CJK route cause of problem in the serialiser
• Awaiting review:
  • bug 769604 – C-C font size toolbar button and change increase/decrease size function.
  • bug 1225904 – C-C CJK e-mail with long lines gets corrupted
  • bug 653342 – C-C CJK fix serializer flags, support delsp=yes, tie all CJK issues altogether. Automatically fixes bug 26734
• (Attended Mozilla Berlin “Tech Meeting”: Firefox OS, Telemetry, Servo/Rust)

aceman

Assisting Thomas D. to drive the patches to fix determining the send format (plain/HTML) of outgoing messages:

• bug 136502 – landed
• bug 584313 – needs review in compose.cpp (e.g. Neil)
• bug 1222176 – patch with tests prepared, needs reviews

wsmwk

• 38.4.0
  • built and shipped
  • tracking Lightning related update issues bug 1215828
• new etherpad https://public.etherpad-mozilla.org/p/thunderbird-encryption

rkent

• I was away for a full week for Thanksgiving, just back today, and have a ear infection as well, so has not been a good week. Responding to the pEp proposals, and Mitchell’s post, are my main priorities at the moment.

Friends of the tree

• congrats to kohei who was recognized for “creating the Thunderbird version of the Get the Add-on button” (and has done a ton of work moving dozens of Thunderbird web pages to bedrock)

Action Items

• we should really clean up the module owners and peers at https://wiki.mozilla.org/Modules/MailNews_Core and https://wiki.mozilla.org/Modules/Thunderbird. Candidates for removal: Bienvenu, standard8, sid0, JosiahOne.

Help Wanted

• Support lead
  • Revise lightning articles on SUMO: https://support.mozilla.org/en-US/search/advanced?q=lightning&language=en-US&category=10&category=20&product=thunderbird&sortby_documents=relevance&a=1&w=1 – to query articles that needs change: https://support.mozilla.org/en-US/contributors/kb-overview?product=thunderbird
• Accessibility lead
• persons comfortable (not necessarily technical experts) with Core type issues. Example graphics to guide bug 1195947 Thunderbird hardware acceleration (HWA) issues to be resolved

Retrieved from “https://wiki.mozilla.org/index.php?title=Thunderbird/StatusMeetings/2015-12-01&oldid=1108006”