Closed Bug 1677205 Opened 4 years ago Closed 2 years ago

Determine and implement site isolation policy for Android Fission

Categories

(GeckoView :: Sandboxing, task, P2)

Product:
GeckoView
Component:
Sandboxing
Platform:
Unspecified
All
Type:
task

Tracking

(firefox101 unaffected, firefox102 unaffected, firefox103 unaffected)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox101 --- unaffected
firefox102 --- unaffected
firefox103 --- unaffected

People

(Reporter: cpeterson, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fission:android:m2][geckoview:m86])

Chrome isolates only sites where the user is "logged in" (i.e. site has “important cookies”).

Will we make the same trade-offs in Gecko? The frontend and Privacy teams will need to provide API to determine if a user is "logged in" for a given site.

Tracking this bug for Android Fission milestone M2 (pass tests with Fission enabled).

Priority: -- → P2
Whiteboard: [fission:android:m2] → [fission:android:m2][geckoview:m86]
Severity: -- → N/A

We've decided to only isolate "high-value" sites on Android:

  // Only isolates web content loaded by sites which are considered "high
  // value". A site is considered "high value" if it has been granted a
  // `highValue*` permission by the permission manager, which is done in
  // response to certain actions.
  IsolateHighValue = 2,

https://searchfox.org/mozilla-central/rev/1fb9316c260bddcd5e6aa2ca1b04e46cb5afb7fd/dom/ipc/ProcessIsolation.cpp#63-67

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

Moving Android Fission bugs to the new GeckoView::Sandboxing component.

Component: General → Sandboxing
You need to log in before you can comment on or make changes to this bug.