Summary
Brave browser appears to be suppressing console.log, console.warn, and console.error outputs, even when they are explicitly invoked in JavaScript. This behavior significantly degrades the developer experience by hiding critical debugging signals without any indication that suppression is occurring.
Problem Description
While debugging a JavaScript component, no errors or warnings appeared in the DevTools console, even though the codebase contains multiple console.log, console.warn, and console.error calls intended to surface runtime issues.
Further investigation showed that:
console.log("test"),console.warn("test"), andconsole.error("test")execute but produce no console output (you can check the screenshot below for more context)- The return value is
undefined, as if the call were silently swallowed - No setting or indicator in DevTools suggests that console output is being suppressed
- This happens due to Brave’s privacy shields, not due to code or framework issues
This makes it extremely difficult to debug applications and can lead developers to falsely assume that code paths are not executing.
Expected Behavior
console.log,console.warn, andconsole.errorshould always be visible in DevTools when called (you can check the screenshot below for extra context)- If Brave intentionally suppresses these logs, this behavior should be:
- Clearly documented
- Clearly indicated in DevTools
- Fully controllable by the user
Actual Behavior
- Warnings and errors are silently suppressed
- No console output, no warnings, no indicators
- DevTools gives no hint that logging has been altered by the browser
Impact
This is a deal breaker for developer experience:
- Breaks debugging workflows
- Masks real runtime issues
- Forces developers to switch to Chrome, or any other browser, for JavaScript debugging
System Specs & Browser version
- Current OS: MacOS Tahoe 26.3
- Brave Version: 1.87.188 (arm64)
- Chromium Version: 145.0.7632.76
Thank you for considering this request.
