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
Currently some calls various browsers dev tools make end up in the trace, but having the tools open is useful to pair with features like device emulation. Need to see if there's some way to determine that the caller is tooling to filter such calls from the log.
The text was updated successfully, but these errors were encountered:
antross
changed the title
Support running in Edge with F12 open
Support running with dev tools open
Jul 13, 2018
Some experimentation with new Error().stack suggests this might be possible.
Calls can potentially be ignored if only tracer code is in the stack or if the bottom of the stack is not page code (e.g. marked (native code) in Edge or <anonymous> in Chrome - unclear if Firefox has an equivalent). Care would have to be taken to avoid accidentally ignoring callback contexts and to make sure no non-tooling cases match these patterns.
Currently some calls various browsers dev tools make end up in the trace, but having the tools open is useful to pair with features like device emulation. Need to see if there's some way to determine that the caller is tooling to filter such calls from the log.
The text was updated successfully, but these errors were encountered: