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
We need to discuss the appropriate level of redaction for extension frames in call stacks.
There are three potential options to consider:
Full redaction
Per-frame redaction
No redaction for the main world
Discussion Points:
Is full redaction necessary, or can we consider per-frame redaction?
Should there be no redaction for the main world?
There was a rough consensus in the WebPerfWG that extension content was acceptable if it appeared in a place (main world) where it could be on the stack.
The text was updated successfully, but these errors were encountered:
It seems like per-frame redaction is the best path. That gives signal that there is a problem occurring that interacts with an extension, without exposing what or how.
Lack of a stack entirely feels like it could lead to a lot of issues in trying to interpret what's happening - Were we unable to get a stack? Did the page's processing pipeline drop the stack? Only redact the relevant frames gives something for the site owner to aggregate one instead of having a large "blank" bucket.
We need to discuss the appropriate level of redaction for extension frames in call stacks.
There are three potential options to consider:
Discussion Points:
There was a rough consensus in the WebPerfWG that extension content was acceptable if it appeared in a place (main world) where it could be on the stack.
The text was updated successfully, but these errors were encountered: