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
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
When checking parent windows for the x-wtf-options element (via topWindow.document.querySelector('x-wtf-options');) the browser will throw if the lookup is disallowed by cross origin constraints.
This exception is caught, but if I have Chrome set to break on uncaught exceptions then this creates a lot of friction on every single page load. The only way solution is to disable pausing or disabling the WTF extension.
It doesn't seem like there is a way to probe the outer frame for cross origin lookups, but postMessage should achieve the same results and is relatively lightweight to implement.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When checking parent windows for the
x-wtf-options
element (viatopWindow.document.querySelector('x-wtf-options');
) the browser will throw if the lookup is disallowed by cross origin constraints.This exception is caught, but if I have Chrome set to break on uncaught exceptions then this creates a lot of friction on every single page load. The only way solution is to disable pausing or disabling the WTF extension.
It doesn't seem like there is a way to probe the outer frame for cross origin lookups, but
postMessage
should achieve the same results and is relatively lightweight to implement.The text was updated successfully, but these errors were encountered: