Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [8f88e2f]
Page Load Metrics (551 ± 29 ms)
|
kumavis
left a comment
There was a problem hiding this comment.
- contentscript lockdown logs 3x times via console.log
console.logonly is silenced to explicitly address this (ok to expand to other console methods)- sentry console breadcrumb gathering should still work even if logging to console is ultimately disabled. they override console methods to collect breadcrumb then call original console method, our noop
|
It looks like |
rekmarks
left a comment
There was a problem hiding this comment.
In addition to what @Gudahtt pointed out, we have a number of log statements in contentscript.js that are useful for development in particular.
I'd also hate to lose this one: https://github.com/MetaMask/metamask-extension/blob/develop/app/scripts/contentscript.js/#L42
|
To follow up on my previous comment, if the content script blows up, the inpage script should (as of late) do enough console logging to hold us over in production. |
8f88e2f to
316844e
Compare
Builds ready [316844e]
Page Load Metrics (551 ± 25 ms)
|
Builds ready [31d1dbc]
Page Load Metrics (656 ± 40 ms)
|
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
Builds ready [a73b5b6]
Page Load Metrics (623 ± 26 ms)
|
Logging in the content scripts surfaces to the external page console. SES/lockdown's logging of removals was appearing in the web console on every web page. This fix renders
consoleuseless inside of content scripts to avoid this.