@social @firefox
Did you just shown a tab group tutorial in the what's new page, yet it's apparently still in progressive rollout?

Disclaimer is only on the technical document but not on the landing page.

Since when you started this kind of marketing bullocks?

Firefox #Mozilla

If you have just recently received an update to Firefox on Android, you may find that all of your bookmarks now have sorting enabled with no option to turn it off.

There is a way (at the time of this post) to turn off this function.

Instructions for disabling automatic sorting currently:

1. Open settings.
2. Tap on About Firefox
3. Tap on the Firefox logo 5 times to enable developer settings.
4. Back out to the main settings menu, scroll down to Secret Settings, and tap on that.
5. Find the 'Enable Compose Bookmarks' toggle and turn it off.

It looks like it's something the Firefox dev's have decided that everyone needs this without any other alternatives.

https://connect.mozilla.org/t5/ideas/restore-ability-to-preserve-desktop-bookmark-order-in-firefox/idi-p/83114

Not disappeared actually, but it was whittled down so much it might as well have.

This is what it looks like in Firefox:

And this is what it looks like in Librewolf:
![](https://lazysoci.al/api/v3/image_proxy?url=https%

Basically what the title says. As far as tech knowledge goes, I am probably a 3.5 or 4 out of 10. Hence the ELI5 request.

I am a Firefox browser user, both in my Android phone as well as Windows device - for the same reason as many others ditched Chrome and chose FF (degoogle and all).

Recently I came to know about Fission being offered in FF nightly. It is said that site isolation with fission is far from ready, and this is probably one of the areas where chromium beats it. I read somewhere that FF fission uses multiple processes to separate sites, but they are not really "isolated processes".

All these is surely not making me less confused about how exactly sandboxing/fission/FPI/TCP differ as far as Firefox is considered, so thought of asking this here.

Posting this in the ELI5 community might've been more "correct", but my question being specifically around Firefox, I thought the chances of getting a better answer is higher here.

Apologies if not, and thanks in advan

Estive a testar os separadores verticais no @firefox e acho que isto não é para mim. Voltar ao estilo antigo

Only finding old ways and either Im too untalented or it become obsolete (as someone mentioned in an old comment there)

Summary

We have rewritten over 600 JavaScript event handlers to mitigate XSS and other injection attacks in the main Firefox user interface. This mitigation will ship in Firefox 138. However, blocking the execution of scripts in the parent process is not the end - we will expand this technique to other contexts in the near future. There is still more work to do as the UI requires JavaScript APIs with a high level of privileges. However: We still eliminated a whole class of attacks, significantly raising the bar for attackers to exploit Firefox. In fact, we hopefully just broke someone’s exploit chain.

Estou a testar os separadores verticais no @firefox e sinto-me completamente perdido. Uma simples alteração e o mundo parece ao contrário...

https://www.mozilla.org/en-US/firefox/137.0/releasenotes/

Edit: I found it it occurred somehow when remapping modifiers with my keyd configuration. I remapped it to CTRL ALT ] and it works now.

It says on https://support.mozilla.org/en-US/kb/about-picture-picture-firefox#w_keyboard-shortcuts that the hotkey to toggle PiP is CTRL Shift ]. When I play a video it shows the PiP button, but the hotkey doesn't work. The other PiP keys like seeking and volume work. I'm on Fedora 41 with KDE 6.3.3 & Wayland.

Crossposted from https://www.reddit.com/r/firefox/comments/1jd5nlk/convert_chrome_extension_to_firefox_addon/

There are a number of FF versions and forks that this will work with, but I used FF Beta (I've also confirmed it to work with FF Nightly & Iceraven. Conversely, it did not work for Mull and iirc, it cannot be done using FF Standard Release/Stable)

• Step 1 - have the CRX file for the Chrome extension handy. There are countless Chrome extensions and FF add-ons that will extract it for you.

• Step 2 - install the CRX Installer add-on (or get the XPI file by whatever means) →Extensions→Click CRX Installer→click "Browse"→ select the CRX file*, which should result in the creation of an XPI file.

• Step 3 - go to Settings→About Firefox Beta (or Nightly, Iceraven, etc)→Tap the logo at the top of the "About" section until you see a toast message saying "Debug Menu enabled" (I think 5 taps)

• Step 4 - navigate to "