Firefox

We need to exert more pressure on apple and eu to not remove PWAs. Every signature counts, please sign and share EU has already started a preliminary investigation on this http://archive.today/2024.02.26-223134/https://www.ft.com/content/d2f7328c-5851-4f16-8f8d-93f0098b6adc

I've been having inconsistent crashes for awhile now where the screen will just suddenly freeze and go white, requiring a close/reopen. It's not usually an issue as it's not too frequent, but it's frustrating to have a bunch of tabs waiting to be reopened.

My issue is that I've tried to check google on how to even look up what might be causing it, and it has been very uncooperative.

first: about:crashes. It's empty. I tried to see if there's a way to turn it on. Any links I could find seemed to be outdated as they pointed to about:preferences#advanced. Which isn't present.

second: checked C:\Users\(username)\AppData\Roaming\Mozilla\Firefox\Profiles\(user profile)

First I checked to see if there was just a general log, then I tried to check crashes.

in both places I tried checking, the file was in a mozlz4 format. I am unsure how it is meant to be read. It was also concerning that despite finding a crash file that matched the time of the crash, all it had was a single meaningless line

"mozLz40 8 ô{"v":1,"crashes":{},"countsByDay ð
rruptDate":null}"

I'm assuming it's not meant to be opened in notepad, but the files I saw in datareporting seemed to be much more comprehensive than this.

So what I'm basically wanting to know is: How do you find out the last thing Mozilla tried to do before freezing? I can't determine if it was Mozilla or an extension doing it, and if it was an extension I can't determine which one.

The main issue is that the crash is inconsistent and mostly randomly. Even if I turn off extensions it could take hours to days before anything happens.

cross-posted from: https://lemmy.ca/post/15541577

The extension shinigami eyes is back.

Quick context: the extension allows you to see which profiles are supportive or transphobic and it wasn’t updated for 2 years.

I was worried it was abandoned. Hopefully we can get Ecosia and Lemmy supported and have it expanded it to cover racist/sexist profiles soon. I would like to donate to the developer if I could.

It is my favourite Firefox extension because it would protect you from seeing all the hate online and prevent unintentionally supporting a slimy transphobe😡 and it literally reveals to you people’s true colours.

2/10/2024

*support for blue sky *updated bloom filter *Fix colonization of Tumblr tags

Firefox for Android has been a disappointment in the mobile browser world for a while now. Let's go through the many reasons why Firefox for Android just isn't measuring up:

1. Android's security measures are lackluster. It's like leaving a toddler to guard a candy store - not very effective.
2. Certificate Issues: Firefox for Android is like a friend who never gives you the full scoop. While Chrome reveals all the details about a website's security certificates, Firefox leaves users in the dark.
3. Engine Rewrite Fail: Firefox for Android attempted to one-up Chrome by rewriting their engine, but the result was a flop bigger than my last cake-baking attempt.
4. No Mute Tab Option: Firefox for Android doesn't offer any way to mute tabs, a feature that Chrome has had built-in for ages.
5. Limited Extension Support: Firefox for Android is trying to lure users away from Chrome by supporting 450 extensions, but browsers like Yandex, Samsung Internet, and Kiwi have offered full extension support for years. Firefox is late to the party, and their limited selection might not be enough to sway users who value extensive customization.
6. Unclear Address Bar Search: When you search in the address bar of Firefox for Android, only the search term is displayed, making it difficult to ascertain if the URL is legitimate or not.
7. Persistent Full-Screen Bug: The full-screen bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1797340) has been hanging around Firefox for Android for years, and they're slower than a sloth when it comes to fixing it.
8. Lackluster Design: Firefox for Android's design is like a cheap knock-off of a premium product.
9. Analytics Overload: Firefox for Android has both Google and Firefox Analytics baked in. Talk about bloatware.
10. Compatibility Issues: Firefox for Android breaks more sites than a bull in a china shop, Compatibility is not its strong suit.
11. Bookmark Management Troubles: Firefox for Android's limitations on editing bookmarks are frustrating. Unlike other browsers, it doesn't allow users to edit bookmarks while searching, making the process cumbersome and inefficient. Although it lets you select multiple bookmarks, the only available option is to delete them - other options mysteriously vanish. Furthermore, the inability to change the position of bookmarks makes organizing your favorites a tedious task. These limitations hinder the overall user experience and leave Firefox for Android lagging behind its competitors in terms of bookmark management.
12. Limited Customization: Firefox for Android claims to be "customizable," but it doesn't offer any significant customization options that Chrome doesn't already have. While Firefox does provide some basic customization features, such as enabling or disabling the shortcuts and jump back in features on the homepage, these options are also available in Chrome. In fact, Chrome offers additional customization features like moving the search bar to the bottom, adding widgets to the home screen, and a dark mode. Thus, Firefox for Android falls short in terms of offering anything truly unique or groundbreaking in the realm of customization.
13. The home button located near the address bar is a persistent eyesore, refusing to disappear even when you want it to. This inflexibility contradicts Firefox for Android's claim of being "customizable," leaving users frustrated and disappointed.
14. No Tab Groups: Firefox for Android is stuck in the past, with no option for tab groups.
15. View Lists of All Websites: Firefox for Android lacks a feature that allows users to easily view lists of all websites saved, cached, or cookie-stored on their device. This can be inconvenient for users who want to manage their online content effectively. The absence of this feature may make Firefox less appealing to users who prefer browsers with more comprehensive options for data access and control.
16. No Split-Screen UI: Want to use Firefox while doing something else simultaneously? Unfortunately, you can't because the UI won't adapt properly to a split-screen mode.
17. No "New Window" Feature: Unlike Chrome, Firefox for Android doesn't have the "New Window" feature that allows users to open a new instance of the browser while using another app. In Chrome, you can access this by opening the menu (the "hamburger" icon) and selecting "New Window," which will open a second Chrome window. Even if Firefox had this feature, its UI issues would likely prevent you from accessing it, as the UI would be outside the reachable area in a split-screen mode.
18. Outdated Tablet UI: Don't expect a modern tablet UI from Firefox for Android - it's still living in the 2000s.
19. Poor WebAssembly Support: Firefox for Android struggles with WebAssembly, leading to more issues than solutions.
20. Lack of Complete Video Format Support: Firefox for Android doesn't support all video formats, leaving users frustrated and searching for alternative browsers.
21. No Offline Dino Game: Firefox for Android takes itself too seriously to include a fun offline game like Chrome's Dino game.
22. Unreliable Cached Pages: Firefox for Android's cached pages are about as reliable as a broken compass. You're better off using smoke signals.
23. Bloated and Slow: Firefox for Android is more bloated than Chrome, making it slower and less efficient.
24. All Talk, No Action: Firefox for Android is like a friend who always promises to do better, but never follows through.
25. Clumsy Performance: Firefox for Android is like a clumsy waiter - always dropping the ball. Stick with Chrome, folks. It may not be perfect, but at least it won't leave you hanging.

Some Firefox fans are attempting to manipulate me into developing features myself, so they can benefit from my work and free time. They seem unwilling to contribute or offer support, and expect others to do all the work for them. It's disappointing that they can barely type a few words before complaining about fatigue, yet they expect others to dedicate their time and effort to developing features for their benefit.

The only addons I've been finding are ones that block based on specific urls, domains, or a few glob patterns. I want to specify any regex.

Normally I want to accept most cookies and not delete them.

There are two sites that I want to delete cookies when I navigate away from them.

If I outright block cookies on these sites, they don't work properly.

I've tried a few cookie extensions and can't figure out how to basically whitelist everything except these two sites without manually whitelisting everything.

Okay hear me out. What if we all chipped in 5 bucks to @firefox? How many people would it take to fund it well enough so they don’t have to do layoffs? I get it, the FOSS community wants the “F” part but we all should contribute some for good infrastructure. And the idea that search engine payments from Google is what keeps Firefox afloat should worry us all. We need browser engine diversity if the web is going to stay open and not littered with walled gardens any more than it already is.

Specifically, Mozilla plans to scale back its investment in a number of products, including its VPN, Relay and, somewhat remarkably, its Online Footprint Scrubber, which launched only a week ago. Mozilla will also shut down Hubs, the 3D virtual world it launched back in 2018, and scale back its investment in its mozilla.social Mastodon instance. The layoffs will affect roughly 60 employees. Bloomberg previously reported the layoffs.

Yo, wtf. Their VPN, Relay and Monitor are basically the only Mozilla services I'd use and pay for. To me this sounds like this is the wrong direction. What do you guys think?

(On Windows anyway, don't know if different on Linux)

Just wanted to share that as a user of both Firefox and Chrome, it's one thing that makes me hate switching to Firefox. I often need to use two different profiles and the way Firefox does it sucks.

With Chrome I've got two shortcuts (that Chrome creates by activating an option) pinned to my taskbar that look distinct from one another and the instances that I open are combined under their respective profile shortcuts.

With Firefox I need to manually create two shortcuts, assign two distinct icons to differentiate them, change some properties so they open the right profile, pin them and because they're "regular shortcuts" instead of the default Firefox launcher shortcut, when I open the program I end up with a third Firefox icon in my taskbar (it does not open under the shortcut I used, it acts as if I clicked a shortcut on my desktop) where all instances get merged together no matter which profile they're associated with.

As the title says, I'm wondering if anyone knows how to block these annoying menu notifications/dots in android Firefox Nightly?

They happen in regular android Firefox too, but I was hoping there would be some setting in Nightly that could disable them.

Edit: some typos

Tab Manager Plus Set to "Open in own tab by default" Set to "Dark mode" Set to "Vertical view" -- very important

You can live search your tab titles to select them

You can open all selected tabs in their own window

You can close selected tabs

You can "discard" tab contents (different from close, the tab is there but content is gone)

You can highlight/select duplicate tabs

You can hide not selected tabs

You can pin selected tabs (unfortunately, they still only appear on the one window they are pinned to, they just get pinned to the left of the tab bar)

You can drag and drop selected tabs to another window of your choice, both the representation of that window in the TMP tab, but also into the other firefox window itself. That means, drag and drop from here, is the same as pulling out a tab out of a normal firefox window !

Cannot search text inside of tabs, especially not sleeping tabs

Sometimes I press the TMP button and I just get a bluegreen screen, doesn't work until I close many windows and tabs

I would prefer real dark mode with my preferred colours

I would like to easily drop&close tabs into bookmark folders reliably !

I'm out of ideas on how to fix this, every now and then my Firefox browser gets a random white border around it. Windows 11, no compatibility mode active for the application.

When I maximize and minimize the window it goes away for a while.

One possible hint: This has started to show up after adding a third display (a 4K TV) to my setup. Even if the TV is fully off. But the TV is the only display which has a different resolution scaling active (all other displays are at 100%).

I mean like why? Just open and update when I'm done that's what every other browser does. Stop making me wait to use the Internet firefox!

I'm just scared that they're saved with reversible encryption on the disk, then malware could steal them

Anytime I search for an addon via the search box in settings > add-ons manager I get all these theme results. Here is a search for "syntax" (via the add-ons manager) I had to make it very zoomed-out to fit long page into screen cap:

I use themes personally to visually differentiate between profiles. And I have nothing against fun and frivolous user customizations. Am not hating on the concept.

I am curious about why they are so aggressively pushed so that they show up be default when trying to search for add ons you need to toggle off every time. Searching for an add-on to do something and searching for a theme that has some keyword included seem to me like totally different tasks and mixing them up is a strange choice.

Is this like a major things firefox thinks people like about it? Do people like it?

Mozilla Corp., which manages the open-source Firefox browser, announced today that Mitchell Baker is stepping down as CEO to focus on AI and internet safety as chair of the nonprofit foundation. Laura Chambers, a Mozilla board member and entrepreneur with experience at Airbnb, PayPal, and eBay, will step in as interim CEO to run operations until a permanent replacement is found.

https://archive.is/rmMEb

Official Blog Post: A New Chapter for Mozilla: Focused Execution and an Expanded Role in Charting the Internet’s Future

Since version 118+, Firefox introduced FPP (Finger Printing Protection) which is in short water downed version of RFP (Resist Finger Printing).

FPP is enabled by default from version 119 onwards if you enable ETP (Enhanced Tracking Protection).

FPP randomizes canvas data subtly than RFP, which is why RFP breaks some sites. So, my question is, if we allow canvas data extraction for a broken site will it fallback to FPP's subtle canvas randomization, or allowing it will expose canvas data completely if we have ETP enabled?

Relevant link: https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting

Edit: More info about HTML5 canvas fingerprinting https://webbrowsertools.com/canvas-fingerprint/

I stand alone with Union Jack held high being battered by the winds of Simplified English. I WILL NOT FALTER! Fighting on beaches, cliffs of Dover! Tea and crumpets Albert! Queen and Country!!!

Any ideas people?

Just sharing about of, what is for me the, best player extension for youtube that was down for a while but seems to be working again.