Firefox Next - ciekawe zmiany

[krystian3w]

A ten uśmiercą lub dopiszą się jako współautorzy:

https://addons.mozilla.org/addon/polish ... ictionary/

Niby mają jeszcze z 2 miesiące na negocjacje by starzy właściciele wgrali uaktualniony XPI (by nie pobierać go z FTP).

[Judykator]

A te wynalazki w pasku wyszukiwania to od której wersji będą? Albo może już są (mam 139) tylko trzeba je jakoś włączyć?

[dexter]

Chyba w pasku adresu. Chodzi o preferencję browser.urlbar.scotchBonnet.enableOverride, można spróbować ją uruchomić.

Ja osobiście to wyłączam.

[Judykator]

Dziękuję. Zapewne o to chodziło. Jutro sprawdze.

[krystian3w]

Na plus jest tylko ułatwienie dla uruchom ponownie, bo tak to używam zakładki do about:support jaka umie psuć na sekundę audio (pierdzi jakbym miał sprzęt z lat 50.).

[dexter]

Windows users with certain NVIDIA graphics adapters and multiple monitors running at mixed refresh rates may see graphics corruption after updating to Firefox 139. As a temporary workaround, set the gfx.webrender.dcomp-win.enabled preference to false in about:config and restart Firefox. This issue will be addressed in Firefox 139.0.1.

[dexter]

On behalf of Mozilla's WebGPU team, I intend to let WebGPU ride the trains to release in Firefox 141 on Windows. Other platforms will follow as soon as practical.

Tracking bug: webgpu-mvp.

Availability: WebGPU has been enabled in Firefox Nightly on all platforms since April 2023, and was enabled on Windows in Firefox 140 Early Beta without incident.

Specifications:

• Content API: https://www.w3.org/TR/webgpu/
• WebGPU Shading Language (WGSL): https://www.w3.org/TR/WGSL/

Working group: WebGPU is being standardized by the “GPU for the Web Working Group”, under the auspices of the W3C:

• GPU for the Web Working Group: https://www.w3.org/2020/gpu/
• GPU for the Web Community Group: https://www.w3.org/community/gpu/

Platform coverage: Firefox should eventually support WebGPU on Windows, macOS, Linux, and Android. Apple is working on an implementation in WebKit for iOS, which we expect to inherit (when it ships in Safari) in Firefox for iOS.

Although the committee has taken care to ensure that WebGPU can be implemented for a wide majority of systems, there are some GPUs and drivers that are not capable enough to run WebGPU. Like WebGL, when a browser cannot find any suitable GPUs, a WebGPU implementation may decline to offer any “adapters” for content to use. GPU-less software implementations might be added in the future.

Standards Compliance: Firefox's compliance with the WebGPU specification has improved to the point that most apps and samples work without modification, and we believe it will work well for most content. We are actively addressing the remaining compatibility issues as identified by the Web Platform Tests and various applications of interest.

Developer tools: At the moment, there is no Devtools support for WebGPU, nor are there any concrete plans for such.

[dexter]

Text-Fragments: Enable creating Text Fragments on Nightly

[krystian3w]

Wyjdzie, że to będzie chyba 3. przeglądarka co ma generator.

Jak komuś nie przeszkadzają błędy, to już można włączyć w Firefox 140:

Kod: Zaznacz cały

dom.text_fragments.create_text_fragment.enabled

viewtopic.php?f=15&t=48366&p=251050#p251050:~:text=dom%2Etext%5Ffragments%2Ecreate%5Ftext%5Ffragment%2Eenabled

W starszych może być mocniej zbugowane (osoby co nie chcą zaktualizować przeglądarki z wydań 131-139 do nowszego).

[dexter]

browser.urlbar.trustPanel.featureGate = true

Firefox is on guard 1.png

Firefox is on guard 2.png

[dexter]

AI Mode

Screenshot 2025-08-07 at 09-46-22 All MoCo Monthly Meeting - August 6 2025.png

[dexter]

As of this week web apps in Firefox has been enabled by default for Windows!

Platforms:
Windows (non-MSIX/Windows Store)
Linux/MacOS to follow later.

Schedule:
Riding trains for Fx143.

How it works:
Web apps for Firefox - working title Taskbar Tabs - allows creating minimalist site-styled window pinned to the taskbar. This is analogous to common use cases for PWAs and leverages similar technologies such as web app manifests.

Web apps are best though of as a special single tab windows attached to a normal profile, with normal access controls. These windows remain in the same profile they were created in, and remember the container they were created with.

The pref now defaulted on is `browser.taskbarTabs.enabled`.

More Information:

• [Meta] Taskbar Tabs - Bug 1915736
• Enabled by default - Bug 1980306
• [Experimental] Firefox now supports Progressive Web Apps on Windows

[krystian3w]

No to lipa, jak będą agresywne jak część starego push, że ikonka obok traczy się nie tylko trzęsie.

Pewnie trzeba setki witryn dopisywać do:

Kod: Zaznacz cały

dorzeczy.pl##+js(aeld, install, function)

[tragivictoria]

Oooo! PWA! Szkoda, że na Linuxa to trafi później

[dexter]

Split View

Screenshot 2025-09-07 at 14-07-28 Split View Implementation Discussion.png

[krystian3w]

Strasznie grube, ciekawe czy nie zapomną usunąć testowego CSS.

[dexter]

Uspokajam: Na pewno zapomną.

Bug 1984696 - Add styling of tabs in a splitview in vertical and horizontal modes
Bug 1986942 - Split view content panel styling

[dexter]

Nowy dekoder JPEG XL napisany w rust.

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

[dexter]

Screenshot 2025-09-19 at 19-42-51 Ustawienia.png

[dexter]

Hey, everyone. Anthony here from Firefox. On behalf of the Firefox team, I'm excited to announce that AI mode is getting closer to launch.

If you're not familiar with how our releases work, we follow a pattern where we have to start shipping code while before it features released. And since we have a culture of building in the open. Developers and followers who are interested in our work will be able to see this code in Mozilla Central, which is basically our repository for code.

So in order to hit the March 26, 149 ship date code will start landing in Mozilla Central no later than November 17th.

So even though I mode won't be out there as a working feature, people will begin to discover the work.

And I think that's great. So I think it's a good opportunity to involve our community, get feedback and get them involved in the process.

And so with that in mind, we've been working with our marketing and comms teams to get better prepped so well, a web page that invites people to sign up via email. Stay in the loop. Get early access, test the product, give us feedback, and hopefully that can help us keep refining it toward the March launch date. We're also going to have a post in Mozilla Connect to hear from our community, and invite them to be part of this process.

So knowing that this might be no big deal to some, but controversial to others, I want to make sure you're all in the loop now.

First. You know I mode is an option. If they're not interested, users can turn it off.

We are working on making our settings easier to use and kind of have like an off button off switch for AI.

It's a nice entry point for curious people to kind of opt into.

Firefox is a trusted place, and we're thinking through ways to kind of ease that burden with model choice. You know, could you have a smart model? Could you have an efficient model? Could you have one that's good to summarizing? They don't necessarily need to know what model it is in the background, but they could if they want. And so we're just thinking through those different types of user experiences.

Now it's going to take a lot of work over the next few months to get there.

But we're gonna listen to our community, and try to involve them as we continue building.

So at this moment, I'm excited about where things are and where they're headed.

And the team is putting in a lot of work to make it happen.

So we'll share more this week on how you can stay in the loop and how you're going to put the effort.