konform-browser/source
3
34
Fork
You've already forked source
5

UI: Expand and improve Privacy Settings #25

Manually merged
konform-browser merged 3 commits from next-level-fingerprinting-settings into dev 2026年03月21日 06:41:28 +01:00
Owner
Copy link

Description

Restructuring and enrichment of privacy settings.

  • ui/prefs: Add toggles for first-party isolation (FPI) under new subsection Privacy & Security -> Browser Privacy -> Fingerprinting
  • ui/prefs: Move ResistFingerprinting (RFP) toggle from Konform -> Privacy to Privacy & Security -> Browser Privacy -> Fingerprinting
    • RFP relates and interacts with ETP enough that they should be colocated in UI.
  • fix(ui/prefs): FPI warning dynamically shown/hidden as privacy.firstparty.isolate enabled/disabled
  • ui/prefs: Reorder cookie/history settings so related and interacting features are next to each other
  • Move up "Cookie Banner Blocking" to be above "Cookies and Site Data" section
    • So that it can be close while "History" takes its position
  • Move up "History" to be below "Site Data" section
    • Their settings relate so they should be colocated

Related

References

First-party Isolation (FPI)

Screenshots

Konform pane

konform-prefs-fpi1

Browser Privacy settings

konform-prefs-fpi2

konform-prefs-fpi3

History settings

konform-prefs-history1

## Description Restructuring and enrichment of privacy settings. - ui/prefs: Add toggles for first-party isolation (FPI) under new subsection `Privacy & Security -> Browser Privacy -> Fingerprinting` - ui/prefs: Move ResistFingerprinting (RFP) toggle from `Konform -> Privacy` to `Privacy & Security -> Browser Privacy -> Fingerprinting` - RFP relates and interacts with ETP enough that they should be colocated in UI. - fix(ui/prefs): FPI warning dynamically shown/hidden as `privacy.firstparty.isolate` enabled/disabled - ui/prefs: Reorder cookie/history settings so related and interacting features are next to each other - Move up "Cookie Banner Blocking" to be above "Cookies and Site Data" section - So that it can be close while "History" takes its position - Move up "History" to be below "Site Data" section - Their settings relate so they should be colocated ## Related - Follow-up to: https://codeberg.org/konform-browser/source/pulls/24 - Resolves: https://codeberg.org/librewolf/issues/issues/1985 https://codeberg.org/librewolf/issues/issues/2328 - Only keying by `Origin` (as "dFPI" does) is not sufficient as it does not consider first-party domain. See [Bug 1330467](https://bugzilla.mozilla.org/show_bug.cgi?id=1330467). ### References #### First-party Isolation (FPI) - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/20317 - https://bugzilla.mozilla.org/show_bug.cgi?id=1308607 - https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40123 - https://bugzilla.mozilla.org/show_bug.cgi?id=1590107 - https://codeberg.org/librewolf/issues/issues/1985 - https://gitlab.com/librewolf-community/browser/common/-/work_items/5 - https://codeberg.org/librewolf/website/issues/106 - https://codeberg.org/librewolf/issues/issues/2173 ## Screenshots #### Konform pane ![konform-prefs-fpi1](/attachments/b98e0ce5-0d5a-44d4-ad2a-1f7bad7cbdeb) #### Browser Privacy settings ![konform-prefs-fpi2](/attachments/17013cd1-8721-4c62-8bd1-06c6059a1e66) ![konform-prefs-fpi3](/attachments/54eea684-b2d3-4091-a057-c40e9b2e75d4) #### History settings ![konform-prefs-history1](/attachments/7c134122-fec5-4de9-86d4-84c4a5299085)
sarge force-pushed next-level-fingerprinting-settings from e3c7557b96
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
to f5ac969381
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026年03月21日 05:02:01 +01:00 Compare
Author
Owner
Copy link

Removal of checkbox Always use private browsing mode for semi-broken feature to be done in follow-up prior to releasing this.

Removal of checkbox `Always use private browsing mode` for semi-broken feature to be done in follow-up prior to releasing this.
sarge force-pushed next-level-fingerprinting-settings from f5ac969381
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
to a3c5100166
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026年03月21日 06:23:14 +01:00 Compare
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Feedback Wanted
Good First Issue
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
 The priority is critical
Priority
High
 The priority is high
Priority
Low
 The priority is low
Priority
Medium
 The priority is medium
Reviewed
Confirmed
 Issue has been confirmed
Reviewed
Duplicate
 This issue or pull request already exists
Reviewed/Has solution
Solution exists. Solution may require user intervention.
Reviewed
Invalid
 Invalid issue
Reviewed
Won't Fix
 This issue won't be fixed
Status
Abandoned
 Somebody has started to work on this but abandoned work
Status
Blocked
 Something is blocking this issue or pull request
Status
Need More Info
 Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
konform-browser/source!25
Reference in a new issue
konform-browser/source
No description provided.
Delete branch "next-level-fingerprinting-settings"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?