Filtering Chrome extension ReportingObserver events?
See original GitHub issuePackage + Version
-
@sentry/browser
-
@sentry/node
-
raven-js
-
raven-node
(raven for node) - other:
Version:
4.0.4
Description
Is it possible to filter out ReportingObserver events from Chrome extensions like we can with regular Sentry errors? We just got one like:
{
anticipatedRemoval: 2019-03-12T04:00:00.000Z,
columnNumber: 307,
id: ElementCreateShadowRoot,
lineNumber: 2,
message: [Filtered],
sourceFile: chrome-extension://mgijmajocgfcbeboacabfgobmjgjcoja/content.min.js
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Event Filtering by criteria other than URL - Google Groups
When adding a listener for various events (e.g. webNavigation.onCommitted), it's possible to supply an filter that prevents the event from being dispatched ...
Read more >chrome.events - Chrome Developers
The chrome.events namespace contains common types used by APIs ... Filtered events are intended to allow a transition from manual filtering code like...
Read more >ReportingObserver - Web APIs - MDN Web Docs
Returns the current list of reports contained in the observer's report queue, and empties the queue. Events. This interface has no events that ......
Read more >Try out our new features page - Chrome Platform Status
Allows web developers to use WebUSB API when responding to extension events by exposing WebUSB API to Service Workers registered by browser extensions....
Read more >JavaScript - Docs - Sentry Documentation
Sentry uses Releases to match the correct source maps to your events. ... of common ignore rules for everyday things, like Facebook, Chrome...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Worth noting here that #1713 removed ReportingObserver from the defaults, so starting with v4.3.0+ this shouldn’t be an issue anymore 😄
You’re right. Updated 😃 Thanks!