Firefox

For example if I were to go to Facebook, you will ask for my location data, and I will say no and never ask again.

Then I go back and it just keeps asking.

Basically every website I visit this happens to.

Is there not a way to just have firefox absolutely stop Facebook from asking again?

Thanks so much for your help

@firefox I'm using this extension called New Tab Override and just saw that the dev complained a few years back about how it wasn't possible to highlight the url of a newly opened tab and there hasn't really been any recent response, will I ever see this? So far I had to reprogram my brain to type Ctrl + A right after the Cttl + T

This is the second such email I have received recently. Seems legit but I don't recognize the domain in the link to sign, and it seems like the people who make Firefox would know that the people who use Firefox would be hesitant to click. IDGI. Anyone else getting these?

Edit 2024-04-10: Got a new email today and it appears all the links now go to links dot mozilla dot org. I won't flatter myself that this post had anything to do with that, but maybe the same thought occurred to someone at Mozilla. Nice. ✌️

Why on earth doesn't Firefox on android properly support navigate.share, IE it won't send across the text property and if you don't put a URL in there it just sends blank, even though the .canShare returns true. You can see various bugs raised and closed about this, a major reason to make people not use the browser and I just can't see why?
@firefox #FireFox #JavaScript

I'm signed into Firefox on 4 devices. I can send tabs between all of them except from my work computer to my phone (other direction works). I can see the tabs open on my computer from my phone and tap to open it on my phone, but if I "send tab" from computer to phone, it never arrives.

I tried signing out on my phone and back in. Didn't work.

What else can I do to troubleshoot?

The select-after-closing-current addon is a way to pullout a random tab out of a window, which will not change the tab that was visible in that window.

However, what it does is any closed tab, it will select the previously seen tab no matter what.

The reason for my question, I would like to know if it is possible for the add-on to have a different behaviour for closed tabs from pulled out tabs.

I wish, when I close a tab, to always select the tab to the right. But when I pullout a tab, I wish to always see the tab that was visible before the pullout.

#experiment tagging @mozilla @mozilla @firefox @firefox to see if this post shows up on #lemmy .

Apparently your mastodon posts show up on Lemmy under the right circumstances (tagging a Lemmy community). 🤞

Edit: if I remove the tagging, will the post magically disappear from Lemmy too?

Edit:
For mastodon users wondering about this, here's the corresponding Lemmy thread: https://lemmy.ml/post/13358920

Mastodon thread for Lemmy users: https://fosstodon.org/@thegreybeardofthetree/112120405122806398

Ref: https://social.vivaldi.net/@bittin/112118062570031583

There used to be an addon, "Open tabs from clipboard URLs" but I can't seem to find it anymore.

The best I find now is, an addon that opens a box, then you paste your URLs in it, then you press a button.

That's not what I want. I want a toolbar button, I press it, the tabs open.

So that I can opens large blocks of URLs.

Also, I would like another addon which opens large blocks of URLs but does not load them immediately.

I have LoadOnSelect3 for this, but the problem with that one, is that it opens special moz:// pages until you load the tab. And that breaks searching and filtering tabs because the tab title and URL are not the real ones.

For instance, in the settings page for Tab Session Manager, you can click an upload button to upload JSON session files from your device to the addon. I looked up if UBlock Origin Lite (the re-implementation of UBlock Origin with Manifest v3) supports custom filter lists and all the results said no it can't due to the limitations of Manifest V3. OTOH I found a StackOverflow post and Google Groups discussion saying its possible with the filesystem API.

Everytime I want to love @firefox , I realize that it doesn't support View Transitions API 😭😭😭😭😭😭😭

#web #firefox #chrome #browser #javascript

Onerep is a privacy monitoring service/ privacy provider that Mozilla partnered with for their Mozilla Monitor service.

Yesterday, Brian Krebs (a cybersecurity journalist) dug into Onerep and found that the CEO is a shady Belarussian. Dimitri Shelest, CEO, of Onerep owns multiple "people searching" websites. Shelest has also been linked to aggressive spam and affiliate marketing emails.

Onerep's reputation is shady due to their CEO's multiple conflicts of interest. At worst, Onerep is sucking your personal information. At best, you're paying for a service that doesn't do anything. Either way, I would not trust Mozilla Monitor service .

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.