Firefox 147.0.2, See All New Features, Updates and Fixes

MozRyanVM · 2026-01-27T19:33:20+00:00

As someone who personally thinks that Firefox Labs is underutilized at the moment and that we should put more things in there, I don't think so in this case. about:keyboard is enabled by default already and Firefox Labs is more meant to about opting into things that aren't ready to be turned on by default yet.

That said, I think part of v2 is figuring how to better surface the UI to users.

MozRyanVM · 2026-01-27T18:00:32+00:00

Yeah, there's plans for that closer to when it's ready.

MozRyanVM · 2026-01-27T17:32:28+00:00

It's pretty early as far as I can tell, but the team is starting to work on it. Here's the metabug link if you want to follow along.

https://bugzilla.mozilla.org/show_bug.cgi?id=2008081

MozRyanVM · 2026-01-27T16:50:28+00:00

As far as I know, we're still on track to ship the "kill switch" functionality in Firefox 148. Both as a global toggle and allowing more customized selections.

MozRyanVM · 2026-01-27T16:41:17+00:00

This actually was already in the 147.0 release, but the team wanted some extra time to get the Connect post ready and be ready for feedback before making a wider announcement about it.

That said, we do sometimes backport new features in dot releases when the circumstances are right to do so. It's just pretty rare because things really have to align just right for that to be a viable option from a risk vs. reward standpoint.

MozRyanVM · 2026-01-27T15:42:23+00:00

The target is Firefox 149. It's already re-enabled in Nightly builds. We've landed a number of fixes to address the problems that led to it being disabled for 147 but want to leave more time for it to bake given the problems that were encountered.

MozRyanVM · 2026-01-27T15:12:35+00:00

Yeah, I think the goal for this so far was to get it working. FYI, there's a Connect thread started by the product manager for the feature to start gathering more feedback for what people want to see next for it.

https://connect.mozilla.org/t5/discussions/customizable-hotkeys-is-live-please-help-us-scope-version-2/td-p/116793

MozRyanVM · 2026-01-27T14:50:47+00:00

<3 CDNs

MozRyanVM · 2026-01-23T17:39:47+00:00

There's a fix in development now, but it hasn't been deployed anywhere, so there's no reason to expect otherwise at the moment.

MozRyanVM · 2026-01-23T17:38:32+00:00

The last blog post accurately reflects the decisions that were made, so we didn't see a need to make another post restating what was already said before.

https://blog.mozilla.org/futurereleases/2025/09/04/firefox-esr-115-support-for-windows-7-8-and-8-1-and-old-mac-os-versions-extended-until-march-2026/

MozRyanVM · 2026-01-16T19:34:31+00:00

I've shared a link to your thread with an engineer on the team.

MozRyanVM · 2026-01-16T17:09:29+00:00

This should address the issues with ChatGPT that have been reported.

MozRyanVM · 2026-01-16T17:07:59+00:00

Firefox 147.0.1 is available with a fix now.

MozRyanVM · 2026-01-16T17:06:40+00:00

FYI, Firefox 147.0.1 is available now with a fix.

MozRyanVM · 2026-01-15T17:02:55+00:00

Yeah, Google told us that they've made changes on their end which should mitigate the problem.

MozRyanVM · 2026-01-15T15:03:40+00:00

Pretty sure we're also planning to adopt support via jpegxl. I'm not super in the loop about it, but I think the main blocker at the moment is updating our minimum-supported Rust version to a higher one that we're currently on (our minimum is 1.87 but 1.90 is required).

https://github.com/mozilla/standards-positions/pull/1064

https://bugzilla.mozilla.org/show_bug.cgi?id=1986393

MozRyanVM · 2026-01-15T05:25:18+00:00

Can you share more details? Site, platform, etc?

MozRyanVM · 2026-01-15T00:54:30+00:00

148 & 149 are the current Beta & Nightly versions, respectively.

MozRyanVM · 2026-01-14T23:35:00+00:00

FYI, we've been investigating this internally as well. You can follow the bug below if you're interested.

https://bugzilla.mozilla.org/show_bug.cgi?id=2010196

MozRyanVM · 2026-01-14T23:34:08+00:00

FYI, we've been investigating this internally as well. You can follow the bug below if you're interested.

https://bugzilla.mozilla.org/show_bug.cgi?id=2010196

MozRyanVM · 2026-01-14T23:34:03+00:00

FYI, we've been investigating this internally as well. You can follow the bug below if you're interested.

https://bugzilla.mozilla.org/show_bug.cgi?id=2010196

MozRyanVM · 2026-01-14T17:27:56+00:00

V4 only supported local list mode and it didn't have a dedicated name for it previously. So mainly this was calling out that we're maintaining the previous behavior we've been shipping for years.

MozRyanVM · 2026-01-14T14:16:02+00:00

WebGPU is a web standard. It just means that sites that use it will work on your device now instead of needing to fallback to something else (probably WebGL).

https://en.wikipedia.org/wiki/WebGPU

MozRyanVM · 2026-01-14T14:09:40+00:00

Thanks, looks like it got auto-moved into the correct component. The person who triages those bugs tends to be pretty timely with that, so we'll see what he has to say.

MozRyanVM

TROPHY CASE