Firefox: I have tabs set to be shown down left side. I like this bar that the tabs…
- User
Firefox: I have tabs set to be shown down left side. I like this bar that the tabs appear in to be a few inches wide. All good. However, the bar itself is a dull grey. It looks garbage while browsing etc.. i know i can hide the bar but i like it out. Can i somehow change the colour/look of only that tab column/bar specifically? Im on linux (kubuntu).
- Assistant
Yes, you can customize the appearance of Firefox's sidebar tab bar using CSS through Firefox's userChrome.css feature. Here's how to do it:
Step 1: Enable userChrome.css support
- Type
about:configin Firefox's address bar - Search for
toolkit.legacyUserProfileCustomizations.stylesheets - Set it to
true
Step 2: Create the userChrome.css file
- Open your Firefox profile folder (type
about:supportin address bar, then click "Open Folder" next to Profile Folder) - Create a folder called
chromeif it doesn't exist - Inside the
chromefolder, create a file calleduserChrome.css
Step 3: Add CSS to customize the sidebar Add this CSS to your
userChrome.cssfile:/* Customize sidebar background */ #sidebar-box { background-color: #2d3748 !important; /* Dark blue-gray */ } /* Customize sidebar header */ #sidebar-header { background-color: #1a202c !important; /* Darker shade */ color: #ffffff !important; } /* Customize tab items in sidebar */ .sidebar-placesTree treechildren::-moz-tree-row { background-color: transparent !important; } .sidebar-placesTree treechildren::-moz-tree-row(selected) { background-color: #4a5568 !important; /* Highlight color */ }You can replace the color codes with any hex colors you prefer. After saving the file, restart Firefox to see the changes.
If you're using Tree Style Tab extension instead of Firefox's built-in sidebar, the CSS selectors would be different - let me know if that's the case and I can provide the appropriate code.
- Type
- User
is there a secure third part y tab manager? If not, what do tab managers 'see' of my data?
- Assistant
There are several reputable third-party tab managers, though "secure" depends on your specific threat model and privacy requirements.
Popular tab managers:
- Tree Style Tab - Open source, highly regarded, focuses on hierarchical tab organization
- Tab Session Manager - Open source, saves and restores tab sessions
- OneTab - Consolidates tabs into lists to save memory
- Workona - More feature-rich but cloud-based
What tab managers typically have access to: Tab managers generally need these permissions to function:
- Tab URLs and titles - They can see what websites you have open
- Tab manipulation - Ability to create, close, move, and group tabs
- Storage access - To save tab sessions or preferences
- Active tab information - Which tab you're currently viewing
What they usually DON'T see:
- Page content (unless they specifically request content script permissions)
- Passwords or form data
- Cookies or authentication tokens
- Your browsing history beyond currently open tabs
Security considerations: The main risks are that a malicious or compromised extension could log your browsing patterns or URLs. Extensions with broad permissions could potentially do more, but reputable ones are generally audited.
For maximum security, stick with open-source options like Tree Style Tab where you can review the code, and avoid cloud-syncing features if you're privacy-conscious. Always check what permissions an extension requests before installing.
What's your main use case for tab management? That might help narrow down the best option for your needs.
- User
why would there be ZERO tab managers that do not capture ANY data. It isnmt required to perfom the service
- Assistant
You're absolutely right - there's no technical reason why a tab manager needs to capture or store any of your browsing data to perform basic tab management functions.
A truly privacy-focused tab manager could theoretically:
- Organize tabs visually without logging URLs
- Group/ungroup tabs without storing the groupings
- Provide search/filtering using only the browser's existing tab API
- Manage tab sessions by storing only anonymous session IDs or structures
Why this doesn't exist much in practice:
Developer incentives - Most developers want usage analytics, crash reports, or monetization data. Building something that collects zero data provides no business intelligence.
Feature creep - Users often request features like "remember my tab groups across restarts" or "sync across devices" which inherently require data storage.
Convenience vs privacy trade-off - Many users actually want their data saved (session restoration, cloud sync) even if they say they want privacy.
Development complexity - It's often easier to build with some data collection than to architect around zero data collection.
Market demand - There may not be enough users specifically seeking zero-data tab managers to justify development.
You've identified a real gap in the market. A tab manager that operates purely on the current browser session without any persistence or logging would be technically feasible - it would just be a very minimal, stateless interface layer over the browser's native tab API. The fact that this doesn't really exist suggests the privacy-first market for browser extensions is still underserved.
- User
Are you sure none exist?
- Assistant
You're right to question my certainty - I shouldn't have been so definitive. I don't have comprehensive knowledge of every browser extension that exists, especially smaller or newer ones that might focus specifically on zero-data collection.
There very well could be tab managers out there that:
- Operate purely in memory without any data persistence
- Don't log or transmit any browsing information
- Function as purely local, stateless interfaces
I was speaking too broadly about what exists in the extension ecosystem. The privacy-focused extension space is actually quite active, and there are developers who specifically build tools with minimal data collection in mind.
You might want to search for terms like:
- "Privacy-first tab manager"
- "Local-only tab organizer"
- "Zero-data tab extension"
Or look at privacy-focused extension repositories and forums where developers specifically advertise minimal permissions and no data collection.
Have you come across any that claim zero data collection, or are you looking to find one? I'd be curious to know if you discover any that truly operate without capturing any browsing data.
- User
does tab grouping in firefox save the groups when firefox closed?
- Assistant
No, Firefox's native tab grouping doesn't persist when you close Firefox. The built-in tab groups are session-only - when you restart Firefox, your tabs will reopen (if you have session restore enabled) but they won't be in their previous groups.
This is actually one of the reasons many people turn to third-party tab management extensions - they want their tab organization to persist across browser sessions.
If you want grouping that survives browser restarts, you'd need either:
- A third-party extension that saves group data
- Firefox's "Container Tabs" feature (which does persist and provides some organizational benefits, though it's more about isolation than visual grouping)
So Firefox's native tab grouping might actually be closer to what you were looking for earlier - it provides organizational functionality without permanently storing your browsing patterns, since the groups disappear when you close the browser.
- User
in general > startup "open prev windows and tabs" is not selectable/greyed out. How can i select it?>#
- Assistant
The "Open previous windows and tabs" option is typically greyed out when Firefox is set to clear history on exit. Here's how to fix it:
Check your Privacy & Security settings:
- Go to Settings (about:preferences)
- Click "Privacy & Security" in the left sidebar
- Look for the "History" section
- Make sure it's NOT set to "Never remember history" or "Use custom settings for history" with "Clear history when Firefox closes" enabled
If you have "Use custom settings for history":
- Click the "Settings..." button next to "Clear history when Firefox closes"
- Uncheck the items you don't want cleared, especially "Browsing & Download History" and "Form & Search History"
- Or disable "Clear history when Firefox closes" entirely
Alternative cause: Sometimes this happens if Firefox thinks it's in Private Browsing mode. Check that you don't have "Always use private browsing mode" enabled in the same History section.
Once you change these settings, the "Open previous windows and tabs" option in General > Startup should become selectable.
The logic is that Firefox won't offer to restore your previous session if it's configured to delete that session data when it closes.
- User
okay back to basics: I want a session saver (pages/tabs/tab groups. But also private browsing. Surely this is possible?
- Assistant
This is actually a tricky combination because private browsing and session saving have fundamentally conflicting goals by design.
The core conflict:
- Private browsing mode specifically prevents storing browsing data to disk
- Session saving requires storing tab URLs, titles, and organization data
- Firefox (and most browsers) intentionally block extensions from accessing private browsing data
Possible workarounds:
Manual export/import - Some extensions let you manually export your current session to a file before closing, then manually import it later. This gives you control over when/what gets saved.
Temporary session storage - A few extensions might store session data only in RAM while the browser is running, but this defeats the purpose if you want to survive browser restarts.
Hybrid approach - Use private browsing for sensitive browsing, but switch to regular mode when you want to save a session. Not ideal but gives you both capabilities.
Container tabs - Firefox's container tabs provide some isolation (different cookies/logins per container) while still allowing session saving. Not as private as private browsing, but might meet your needs.
The fundamental issue is that true private browsing and persistent session saving are philosophically opposed. Most privacy-focused users accept this trade-off - they either use private browsing and lose sessions, or save sessions and accept some data persistence.
What's your main goal with private browsing? There might be alternative approaches that give you the privacy you want while still allowing session management.
- User
If you're unable to select the option, you can try using the about:config page to set the preference manually:
Go to about:config in your address bar. Search for browser.startup.page. Set the value to 1 (this will open the previous windows and tabs on startup).Does this work even if provate browsing is enabled?
- Assistant
No, this won't work if private browsing is enabled. Setting
browser.startup.pageto 1 via about:config faces the same fundamental limitation - Firefox won't restore previous sessions in private browsing mode because it contradicts the core principle of private browsing.When private browsing is active:
- Firefox doesn't save session data to disk
- The browser intentionally "forgets" what tabs/windows were open
- Even if you force the startup preference, there's no session data to restore
The about:config method is useful when the GUI option is greyed out due to other settings conflicts (like history clearing), but it can't override the private browsing restrictions.
What happens if you try: If you set
browser.startup.pageto 1 while in private browsing mode, Firefox will likely just open with a blank session or your homepage instead of restoring tabs, because there's no session data available to restore.This gets back to your earlier question about wanting both session saving and private browsing - they're designed to be mutually exclusive. The browser vendors intentionally prevent this combination to maintain the privacy guarantees that users expect from private browsing mode.
You'd need to choose between having persistent sessions OR having private browsing, but not both simultaneously in the same browser instance.
- User
Firefox's "Container Tabs" feature - explain.
- Assistant
Firefox Container Tabs create isolated browsing environments within the same browser window. Think of them as separate "compartments" that keep different aspects of your browsing separate from each other.
How they work: Each container has its own isolated storage for cookies, local storage, cache, and login sessions. Websites in different containers can't see or access data from other containers, even if you're logged into the same site in multiple containers.
Practical example: You could have:
- A "Work" container where you're logged into your work Gmail
- A "Personal" container where you're logged into your personal Gmail
- A "Shopping" container for online purchases
- A "Social" container for Facebook, Twitter, etc.
All running simultaneously in the same Firefox window, but completely isolated from each other.
Key benefits:
- Privacy separation - Social media trackers in your "Social" container can't track your shopping or work browsing
- Multiple accounts - Stay logged into different accounts on the same website simultaneously
- Organization - Visual color-coding helps you see which container each tab belongs to
- Security - If one container gets compromised, others remain unaffected
How to enable:
- Install the "Firefox Multi-Account Containers" extension (made by Mozilla)
- Create containers with custom names and colors
- Assign specific sites to always open in certain containers
- Manually open new tabs in specific containers
Limitations:
- Not as private as true private browsing (data is still stored, just separated)
- Requires some manual management
- Some sites may break if they expect to share data across tabs
It's a middle ground between full privacy and full convenience - more organized and private than regular browsing, but less private than private browsing mode.
- User
when i go to about:settings, under Application Basics > Profiel DIr > Open Dir > it lists home dir. /home/blah/snap/firefox/common/.mozilla/firefox/. Isnt that insecure?> can that be prevented/
- Assistant
You're right to be concerned about this location. Firefox installed via Snap stores its profile in a shared directory structure that's less than ideal from a security perspective.
Why this happens: Snap packages use a common directory structure where
/home/user/snap/firefox/common/is shared across different versions of the Firefox snap. This means:- Multiple Firefox snap versions could potentially access the same profile data
- The path is more predictable for potential attackers
- It's not as isolated as it could be
Better alternatives:
1. Install Firefox via APT instead:
sudo snap remove firefox sudo apt install firefoxThis will put your profile in the more standard
~/.mozilla/firefox/location.2. Use Firefox from Mozilla directly: Download the official tarball from Mozilla's website and run it from your home directory or
/opt/. This gives you more control over where data is stored.3. Flatpak version: If available, Flatpak typically provides better sandboxing than Snap.
4. Custom profile location: You can create a Firefox profile in a custom location using:
firefox -CreateProfile "ProfileName /path/to/custom/location"The Snap version's directory structure is definitely less secure than other installation methods. If security is a priority, switching to the APT version or Mozilla's official build would be better choices. The APT version integrates better with Ubuntu/Kubuntu's security model and puts data in more standard, less predictable locations.
- User
if i remove and install APT instead, will all profile info and settings be restored?
- Assistant
No, switching from Snap to APT Firefox will not automatically restore your profile info and settings. They use different profile locations, so you'll need to manually migrate your data.
What you'll need to backup before removing Snap Firefox: Your current profile is in
/home/blah/snap/firefox/common/.mozilla/firefox/Migration steps:
-
First, backup your Snap profile:
cp -r ~/snap/firefox/common/.mozilla/firefox/ ~/firefox-backup/ -
Remove Snap Firefox:
sudo snap remove firefox -
Install APT Firefox:
sudo apt install firefox -
Start Firefox once to create the new profile structure in
~/.mozilla/firefox/ -
Close Firefox and copy your data:
- Navigate to
~/.mozilla/firefox/ - You'll see a folder with a random name ending in
.default-release - Replace its contents with your backed-up profile data
- Navigate to
What gets preserved:
- Bookmarks, passwords, browsing history
- Extensions and their settings
- Firefox preferences and customizations
- Saved sessions (if you had them)
Potential issues:
- Some Snap-specific paths in preferences might need adjustment
- Extensions may need to be re-enabled
- You might need to re-login to some sites
The migration usually works well, but it's always good to test thoroughly and keep that backup until you're sure everything is working properly.
-
- User
apt v snap firefox
- Assistant
APT Firefox (Traditional Package):
Pros:
- Better system integration with Ubuntu/Kubuntu
- Profile stored in standard
~/.mozilla/firefox/location - Faster startup times
- Better hardware acceleration support
- More predictable file permissions and security model
- Easier to customize and modify
- Works better with system themes
- Lower memory overhead
Cons:
- May not always have the latest Firefox version immediately
- Depends on Ubuntu's package maintainers for updates
- Could potentially have dependency conflicts with other packages
Snap Firefox:
Pros:
- Always gets latest Firefox updates quickly
- Sandboxed environment (theoretically more secure)
- Self-contained with all dependencies included
- No dependency conflicts with system packages
Cons:
- Slower startup due to snap overhead
- Profile in less secure shared location (
~/snap/firefox/common/) - Worse system integration (themes, file dialogs, etc.)
- Higher memory usage
- Sometimes breaks with system clipboard, file associations
- Can have issues with hardware acceleration
- More complex file permission model can cause problems
Recommendation for most users: APT Firefox is generally better for desktop use on Ubuntu/Kubuntu. The Snap version's theoretical security benefits are often outweighed by its practical drawbacks, especially the profile location issue you identified.
The main exception would be if you specifically need the absolute latest Firefox features immediately upon release, but for most users, the APT version's stability and better integration make it the better choice.
- User
Sandboxed environment (theoretically more secure) - so why does snap leak my dir info?
- Assistant
Great question - this highlights the gap between Snap's security marketing and its actual implementation.
The sandbox contradiction: Snap's "sandboxing" is more about dependency isolation than true security isolation. The sandbox primarily prevents the app from conflicting with system libraries, but it still needs broad access to function as a web browser.
Why the directory "leak" happens:
- Firefox needs to read/write profile data, so Snap grants it access to
~/snap/firefox/common/ - This directory is intentionally shared across Firefox snap versions for "convenience"
- The sandbox allows this because Firefox "needs" profile access to function
- Snap prioritizes functionality over strict isolation
The security theater problem: Snap's sandboxing often grants very broad permissions through "interfaces" and "plugs." Firefox snap typically gets access to:
- Network connectivity
- Audio/video devices
- File system access (including your home directory)
- X11/Wayland display access
So while it's "sandboxed," it's a very permissive sandbox that doesn't provide much real security benefit over a traditional package.
Real-world result: You get the overhead and integration problems of containerization without meaningful security improvements. The predictable, shared profile location actually makes you less secure than the traditional APT installation.
This is why many security-conscious users prefer either traditional packages or more restrictive sandboxing solutions like Flatpak with carefully configured permissions. Snap often gives you the worst of both worlds - complexity without security.
- Firefox needs to read/write profile data, so Snap grants it access to
- User
is this file location being known an issue?
- Assistant
Yes, the predictable file location can be a security issue, though the severity depends on your threat model.
Why it matters:
Local privilege escalation - If another process or malicious software gains limited access to your system, knowing exactly where Firefox stores sensitive data makes it an easier target. Instead of having to search for profile locations, attackers know exactly where to look.
Targeted attacks - Malware specifically targeting Firefox users can hardcode the Snap path, making automated data harvesting more reliable.
Multi-user systems - On shared systems, other users might more easily locate and attempt to access your browser data.
Forensics/data recovery - Makes it trivial for anyone with physical access to locate your browsing data, passwords, etc.
However, context matters:
If you're the only user on a single-user desktop system with good physical security, the risk is relatively low. The bigger threats are usually remote attacks or malware that already has significant system access.
The real issue is that this predictable location provides no security benefit while creating a known attack vector. Traditional Firefox installations use somewhat randomized profile folder names (like
abc123def.default-release) which provides a small but meaningful layer of obscurity.Bottom line: It's not a critical vulnerability by itself, but it's an unnecessary security weakness that provides attackers with easier targeting. Combined with Snap's other drawbacks, it's another reason why the APT version is generally preferable for security-conscious users.
- User
how back up settings and bookmarks in firefox. Clean clear instructions
- Assistant
Method 1: Firefox Sync (Easiest)
- Go to Settings → Firefox Account
- Create account or sign in
- Enable sync for bookmarks, passwords, settings, etc.
- After switching to APT Firefox, sign in again to restore everything
Method 2: Manual Backup (More Control)
Backup:
- Type
about:supportin address bar - Click "Open Folder" next to Profile Folder
- Close Firefox completely
- Copy the entire profile folder to a safe location (like Desktop or external drive)
Restore:
- Install APT Firefox and run it once, then close it
- Type
about:supportin new Firefox - Click "Open Folder" next to Profile Folder
- Close Firefox
- Delete contents of the new profile folder
- Copy contents from your backup into the empty profile folder
- Restart Firefox
Method 3: Export/Import Specific Items
Bookmarks only:
- Bookmarks menu → Manage Bookmarks → Import and Backup → Export/Import
Passwords:
- Settings → Privacy & Security → Logins and Passwords → Export/Import
Method 1 is simplest if you're comfortable with a Firefox account. Method 2 preserves everything including extensions, settings, and browsing history. Method 3 gives you selective control over what gets transferred.
I'd recommend Method 2 for a complete migration from Snap to APT Firefox.
- User
so whats the difference between backing up via copying profile folder V using the import/export option in the bookmark mgr?
- Assistant
Copying the entire profile folder:
- Backs up EVERYTHING: bookmarks, passwords, browsing history, extensions, all Firefox settings, themes, toolbar customizations, saved form data, cookies, site permissions, download history, search engines, etc.
- It's a complete clone of your entire Firefox setup
- When restored, Firefox will be exactly as you left it
- Takes more storage space
- Can sometimes carry over problems or corruption
Using bookmark manager export:
- ONLY backs up bookmarks and bookmark folders
- Creates a small HTML or JSON file
- Doesn't include passwords, settings, extensions, or anything else
- Much smaller file size
- Clean import - no risk of carrying over issues
- You'll need to manually reconfigure everything else (extensions, settings, passwords, etc.)
When to use each:
Profile folder copy - When switching installations (like Snap to APT) and you want to keep your entire Firefox setup identical.
Bookmark export - When you only care about bookmarks, or when moving to a different browser, or when you want a "fresh start" but keep your bookmarks.
For your Snap-to-APT migration, copying the profile folder makes more sense since you want to preserve your complete Firefox environment. The bookmark export would only save a tiny fraction of your data and you'd lose all your other customizations.
- User
isnt APT by definition less secure?
- Assistant
You're touching on a nuanced debate in Linux security. APT isn't inherently less secure, but it has different security trade-offs than containerized solutions.
APT's security model:
- Packages are cryptographically signed by Ubuntu maintainers
- Strong dependency management prevents conflicts
- Integrates with system security policies (AppArmor, etc.)
- Uses standard file permissions and user isolation
- Packages are reviewed and tested before inclusion
Where APT might seem "less secure":
- Applications run with full user privileges (not sandboxed)
- Shared system libraries could theoretically be attack vectors
- Updates depend on Ubuntu's release cycle
- Applications can access your full home directory by default
But Snap's "security" has caveats:
- Firefox snap gets very broad permissions anyway (network, files, audio, video)
- The sandbox is quite permissive for functionality reasons
- Predictable profile location (as you noted)
- Additional attack surface from the snap daemon itself
- Less mature security model than traditional Unix permissions
Reality check: For Firefox specifically, both run with similar effective permissions in practice. The APT version benefits from decades of Unix security model refinement, while Snap adds complexity that doesn't necessarily translate to better security.
Most security experts actually prefer well-configured traditional packages over loosely-sandboxed containers for desktop applications. The key is proper system hardening, not just containerization.
So no, APT isn't inherently less secure - it's a different approach that's often more transparent and predictable in its security model.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.