[notafox]

Also profiles can be configured and used with CLI, no need for UI (old or new).

    ./firefox -CreateProfile "profile-name /home/user/.mozilla/firefox/profile-path/"
    ./firefox -profile "/home/user/.mozilla/firefox/profile-path/"

And, you can run it directly, no need to launch default firefox profile:

Given that /usr/bin/firefox is just a shell script, you can

    - create a copy of it, say, /usr/bin/firefox-hn
    - adjust the relevant line, adding the -profile argument

If you use an icon to run firefox (say, /usr/share/applications/firefox.desktop), you'll need to do copy/adjust line for the icon.

[chimeracoder]

> Also profiles can be configured and used with CLI, no need for UI (old or new).

AFAIK, they can only be created at the command line, not configured. If you want to do things like change default settings or install extensions from the Firefox Add-On store, you can't really do that at the command line.

You can do that by mucking around in the user.js file and manually adding .xpi files to the extensions/ subfolder, but that's probably stretching the definition of "done at the command-line" since most people aren't creating Puppet modules to manage Firefox profiles.

Perhaps someone knows an easier way to do this, though.

[unethical_ban]

Instead of needing to know scripting for a core feature, it would be nice if I could tell the program to ask me every time I open a new window which profile that window used. Right click would have an option like their containers "opening new profile window" .

[panarky]

Right-click on the Firefox icon and choose "Open Profile Manager".

Or add "-p" to the startup command to do the same thing without right-clicking:

    firefox -p

[skydhash]

Better if they would allow some configuration like toggling js by domain. uBlock is great, but I would like first party support.

[HackerThemAll]

NoScript extension...