You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Expected behavior
Not very actionable as the caller cannot observe these console logs
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: