Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Domain Filter Logic within Privacy Sandbox Cookies View (Generalize for All Filters) #895

Open
jlacher opened this issue Dec 13, 2024 · 1 comment
Labels
enhancement New feature or request Feature Request
Milestone

Comments

@jlacher
Copy link

jlacher commented Dec 13, 2024

Feature Request: Improve Domain Filter Logic within Privacy Sandbox Cookies View (Generalize for All Filters)

Summary:

The Privacy Sandbox Cookies view currently displays all domains in the left-hand "Domain" filter section, regardless of which filters are active (e.g., "Scope", "Category", etc.). This can be misleading and create unnecessary cognitive load as users are presented with options that may be irrelevant based on the currently selected filter(s). The "Domain" filter section should be dynamically updated to reflect all active filters.

Problem:

  • When filtering cookies by any criteria (e.g., "Scope", "Category", etc.), the "Domain" filter section continues to list all domains, including those that are not relevant to the active filter combination.
  • This behavior requires users to visually scan through irrelevant options, which is confusing and increases cognitive load.
  • The current functionality gives the impression that there are cookies from these irrelevant domains, when there aren't any within the scope of the active filters.

Proposed Solution:

  • Implement dynamic filtering in the "Domain" section. When any combination of filters is selected (e.g., "First Party" scope and a specific category), the list of domains in the "Domain" filter should be updated to show only domains that have cookies matching all the selected filters.
  • The "Domain" filter list should therefore represent the intersection of all the selected filters, and not the union of them.
  • For example, if "First Party" is selected in the Scope filter, and a Category is selected, only domains that have first-party cookies matching that category should be listed in the "Domain" filter section.
  • This will provide a more focused and streamlined user experience by hiding irrelevant options and making the domain filtering more closely connected to all the active filters.
  • This will also improve usability by directly showing the domain associated with the currently active filter set.

Benefits:

  • Reduces cognitive load by only displaying relevant filtering options.
  • Improves user experience by streamlining the filtering process.
  • Makes the UI more intuitive and less confusing.
  • Provides a more accurate picture of which domains are associated with the active filter combination.
  • Makes the filtering logic more predictable and more connected across all the active filters.

Additional Notes:

  • The current behavior of the "Domain" list could potentially mislead users who may think that domains are relevant when they are not part of the filtered set.
  • This improvement will ensure that the filtering panel is logically connected and acts more in line with user expectations across all available filters.

Example:

As shown in the image below, when "First Party" is selected in the "Scope" filter, domains like ".bat.bing.com" and ".c.bing.com" should not appear in the "Domain" filter. This logic should also be applied for other filters and combined filters.

AohUaHLuaae9osV

@milindmore22
Copy link
Collaborator

milindmore22 commented Dec 18, 2024

Hello @jlacher

We greatly appreciate the detailed explanation and provided example. This perfectly aligns with our objective to deliver a streamlined and user-friendly experience within the PSAT.

By implementing dynamic filtering, the section will accurately reflect the currently filtered set, eliminating any potential confusion regarding irrelevant results.

We will work towards incorporating this feature in our upcoming release.

@milindmore22 milindmore22 added this to the v1.0 milestone Dec 18, 2024
@milindmore22 milindmore22 added the enhancement New feature or request label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Feature Request
Projects
Status: Todo
Development

No branches or pull requests

2 participants