Mozilla Connect Weekly Recap: Top-Voted Ideas (3/6-3/13)

[Jon]

Hey all,

Happy Friday Sunday and welcome to another Weekly Recap here in the Mozilla Connect community!

This post will highlight the top 10 most-voted ideas for the previous week (3/6-3/13). While some are ‘new ideas’ and others are already ‘in review’ (learn more about The Idea Journey here), we encourage you to continue voting and add any input that supports your favorite ideas—the more details, the better.

Here they are…

Take the opportunity of the Nova redesign 🚀 to introduce a "corner rounding" feature! 

Shortcuts for Split View 

Put the AI stuff into an optional add-on 

Mozilla! Allow us to customize the roundness of edges. 

Option to allow extensions to run only on specific websites. 

Feature Request: Fix places.sqlite 80MB Limit & Add True "Keep History Forever" 

Mobile tab grouping 

Sort extensions from Tools menu alphabetically (as in other browsers). 

Firefox ad-blocking in iOS Firefox 

Synced WORK SPACES (or Synced Tab Groups) 

And that's it for this week!

Want to show your support for one (or more) of the ideas above? Click on the idea link, give it kudos, and add your insights.

Is there another idea here on Connect that you think deserves more attention? Tag it in the comment section below.

Or do you have the next great idea for a new feature/feature enhancement/brand new product/you name it? Submit it right here 💡

[gabeweb]

Wow, nice!

[lackey]

I look forward to Mozilla's response to "Put the AI stuff into an optional add-on"

[Tazer_Silvascar]

I can't see them even entertaining the idea. They're probably just acknowledging it for the sake of appearances. But I agree, it would be better to be a completely separate thing, not built-in. After all, we don't know how much of it is already hard-coded into the browser now. So much for Firefox being a light-weight browser. I've definitely seen it chugging at times, when that never used to be an issue.

[gabeweb]

At first, that idea might seem like plenty, but down the line, it could actually be dangerous.

An add-on can be messed with by someone else, or you might even run into a fake version. Even nowadays, people are still clicking shady links and installing weird, fraudulent plugins. It’s also not the first time (and definitely won't be the last) that malicious stuff has slipped into the extension stores.

Ideally, it should just be a built-in feature (staying completely optional), just like it is now.

[Tazer_Silvascar]

The problem there is that you can't say how much of that built-in feature is operating processes in the background without telling you. This is why it would be more sensible for it to be more separated from the browser. Or you know, Mozilla could just supply an AI free build, because quite frankly, just mentioning AI within the application is enough to look at the entire application with suspicion. A much lighter, safer browser would just be that much more appealing for people who don't want their data to be touched by AI.

[gabeweb]

So, let's just say Firefox is "powered by smarter things" instead of "powered by AI" to make it morally acceptable. It's like: "don't call it a browser, it's an explorer, or it's a navigator".

[Tazer_Silvascar]

I don't want things worded differently, that doesn't change a thing. I'm not here to be talked down to like a child. I'm here to ensure that my data is safe. And when Mozilla is permanently adding stuff to Firefox that can just take my data and feed it into their perpetual slop machine, yeah, you bet I'm going to be annoyed that it's there. You might not care for your own data safety, but I care for mine. I'm not here for 'morally acceptable AI' or any rewording of it for false marketing purposes. Nothing short of it being completely detached and 100% optional will be acceptable.

[lackey]

Mozilla put functional containers into an add-on. There's no reason they can't do the same thing here. 

[gabeweb]

---

@lackey wrote:

Mozilla put functional containers into an add-on. There's no reason they can't do the same thing here. 

---

Actually, container functionality is built into Firefox itself rather than being a standalone add-on. The extension simply provides a more robust GUI for management.

[lackey]

Container tabs would have absolutely been impossible without an API in the browser. But what about this new feature? If an extension for tab notes already exists and is already more feature-complete, why does Mozilla have to bake in a clone?

[gabeweb]

---

@lackey wrote:

Container tabs would have absolutely been impossible without an API in the browser. But what about this new feature? If an extension for tab notes already exists and is already more feature-complete, why does Mozilla have to bake in a clone?

---

Because add-ons have limited operability within containers. You can't call a Firefox container inside the sidebar pane, just the main 'container' (or 'process'). Even cookie management add-ons cause some headaches when trying to import, export, or keep cookies between containers.

You're right that containers required a deep API, but implementing tab notes is much more surface-level. It doesn't require complex modifications to the browser's core or the container isolation logic.

Native features don't face the same security sandboxing that add-ons do. Firefox intentionally restricts what extensions can access to keep the browser secure and stable. By 'baking in' notes, Mozilla can offer a feature that works globally across all containers without compromising the security model they've built for third-party developers.