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

Downgrade SharedStorage out of budget log level messages #462

Open
ankwok opened this issue Jan 24, 2025 · 3 comments
Open

Downgrade SharedStorage out of budget log level messages #462

ankwok opened this issue Jan 24, 2025 · 3 comments

Comments

@ankwok
Copy link

ankwok commented Jan 24, 2025

Hello,

As an ad tech with Javascript tags on client websites, we do our best to catch any errors and properly treat them as to not negatively impact the client's website behavior. Clients routinely monitor the console activity on their websites and complain to us when our JS tag produces error messages in the console.

The Shared Storage API has a budgeting mechanism with clearly defined behaviors when we try to perform an operation like selectURL when no budget remains. However, Chrome logs an error when this expected behavior happens. Our JS code cannot catch it since no error is thrown. This is by design otherwise an actor would be able to know whether or not they have any remaining privacy budget.

We would like Chrome to downgrade such logging to warning or info as it is:

  1. Expected behavior
  2. Not very actionable as the caller cannot observe these console logs
@csharrison
Copy link

csharrison commented Jan 24, 2025

cc @alexmturner @dmcardle

@dmcardle
Copy link

Hi, @ankwok, downgrading the severity of this console error sounds reasonable to me.

Could I trouble you to file this as a new issue on the Shared Storage repo? https://github.com/WICG/shared-storage

Thanks!

@ankwok
Copy link
Author

ankwok commented Jan 28, 2025

Done: WICG/shared-storage#223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants