Technology

59135 readers

3635 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

2296

It is essential to stop using Chrome. Under the pretense of saving users from third-party spyware, Google is creating an ecosystem in which Chrome itself is the spyware. (mastodon.world)

submitted 10 months ago by Live_Let_Live@lemmy.world to c/technology@lemmy.world

473 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Fubarberry@sopuli.xyz 1 points 10 months ago (1 children)

Most recent one was visiting https://www.lifetime.com/playsets on Firefox mobile. After going back and forth between the list of playsets and individual playset pages, Firefox stopped loading the list of playsets. I would load in most of the page, but the actual product list wouldn't load. Refreshing and restarting Firefox wouldn't fix it, but the page loaded fine in brave browser so it didn't appear to be a server issue.

Before that one, I had a time where Firefox mobile was completely broken by an update for like a week. Wouldn't load any web pages, reinstalling/resetting user data/etc wouldn't fix it.

I've had websites break on Firefox desktop too, but I don't have any specific examples I can recall right now. I definitely run into more issues with Firefox mobile than desktop though.

[–] FutileRecipe@lemmy.world 1 points 10 months ago

I definitely run into more issues with Firefox mobile than desktop though.

Ah, mobile. I don't use Firefox mobile due to its insecure status, particularly lack of sandboxing:

Avoid Gecko-based browsers like Firefox as they're currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn't have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox's sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn't happening for their Android browser yet.

Source: https://grapheneos.org/usage#web-browsing