this post was submitted on 18 Jun 2024
59 points (91.5% liked)

Firefox

17815 readers
55 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

I heard around the internet that Firefox on Android does not have Site Isolation built-in yet. After a little bit of research, I learned that Site Isolation on Android was added in Firefox Nightly, appearing to have been added sometime in June 2023. What I can't find, though, is whether this has ever been added to any stable versions of Firefox yet. Does anyone know anything about this?

Update: After further research, it appears that Site Isolation is not currently a feature in stable version of Firefox on Android. I don't know with certainty if their information is up-to-date, but GrapheneOS (A well-known privacy/security-focused fork of Android) does not recommend using Firefox-based browsers on Android due to it's (apparently) lack of a Site Isolation feature. A snippet of what Graphene currently have to say about Firefox on Android/GrapheneOS from their usage guide page, is: "Avoid Gecko-based browsers like Firefox as they're currently much more vulnerable to exploitation and inherently add a huge amount of attack surface."

On a side-note, they also say about Firefox's current Site Isolation on desktop being weaker, which I wasn't aware of. "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."

you are viewing a single comment's thread
view the rest of the comments
[โ€“] boredsquirrel@slrpnk.net 30 points 4 months ago* (last edited 4 months ago) (1 children)

Lol

  1. Bug with high priority
  2. A person clones it, assigns themselves
  3. doesnt have time, unassigns themselves
  4. Priority gets set lower
  5. A guy wants to work on it
  6. That guy doesnt work at Mozilla anymore
  7. The bug went from priority P5 to P1 and doesnt block anything anymore

This is really bad. Especially as it seems like not that big of a change.

[โ€“] ahal@lemmy.ca 7 points 4 months ago* (last edited 4 months ago)
  1. doesnt have time, unassigns themselves

Because someone else took over, as the person even says in a comment.

  1. Priority gets set lower

Priority got set back to the priority it was at 4 minutes before. The priority being changed was clearly a mistake.

  1. A guy wants to work on it
  2. That guy doesnt work at Mozilla anymore

OK?

  1. The bug went from priority P5 to P1 and doesnt block anything anymore

It got retriaged. There are processes for this and it's totally normal.

This is really bad. Especially as it seems like not that big of a change.

No it really isn't bad at all. And it's a massive change, the linked bug is a meta bug which means it is simply used to track the actual work. See all the bugs in the depends on section? That's where the real work happens and there has been a ton of progress made.

Also believe it or not, lots of discussion happens outside of bugs. You really have no idea what is going on just by looking at bug activity.