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
The current impl uses the ChromeConsoleMessages gatherer and filters onmessage.type === 'deprecation'.
This works great, but ReportingObserver provides a better structured API intended for observing deprecations. It has other nice feature like buffering (can include deprecations that happen before the observer was added to the page) useful fields like anticipatedRemoval:
Switching to a ReportingObserver-based would set us up nicely for future audits that use the Reporting API: CSP violations, feature policy violations, browser interventions.
The text was updated successfully, but these errors were encountered:
The current impl uses the
ChromeConsoleMessages
gatherer and filters onmessage.type === 'deprecation'
.This works great, but
ReportingObserver
provides a better structured API intended for observing deprecations. It has other nice feature like buffering (can include deprecations that happen before the observer was added to the page) useful fields likeanticipatedRemoval
:Switching to a
ReportingObserver
-based would set us up nicely for future audits that use the Reporting API: CSP violations, feature policy violations, browser interventions.The text was updated successfully, but these errors were encountered: