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 DevTool "sources" tab show the code in just white color (I have the dark mode activated) and the performances while debugging some code are very bad. The same code debugged in Chrome or other browsers is working fine.
Actual result:
As I said, slow performances and something is wrong with colors. See attached pictures.
Expected result:
I except Brave to work like Chromium.
Reproduces how often:
Everytime in every site. I tried unistalling and re-installing the browser in order too see if the problem solve, without success.
@bsclifton says...
This may be fixed now; with Nightly (and it'll work its way down through channels), you can enable remote debugging under brave://settings/privacy. When this is enabled, it should fetch sources
@JacopoSciampi this is fixed in Developer and Nightly versions of the product (NOTE: you have to enable remote debugging under brave://settings/privacy). I created a PR now to uplift this to our Beta branch (1.2, shipping January 6th) since there have been a recent bump in requests: brave/brave-core#4228
Description
The DevTool "sources" tab show the code in just white color (I have the dark mode activated) and the performances while debugging some code are very bad. The same code debugged in Chrome or other browsers is working fine.
Actual result:
As I said, slow performances and something is wrong with colors. See attached pictures.
Expected result:
I except Brave to work like Chromium.
Reproduces how often:
Everytime in every site. I tried unistalling and re-installing the browser in order too see if the problem solve, without success.
Brave version (brave://version info)
Other Additional Information:
Miscellaneous Information:
Photo taken in Brave
Photo taken in Chrome (79.0.3945.79)
The color being this different can mean that something didn't load up properly (I guess) but I haven't found a way to solve this.
The text was updated successfully, but these errors were encountered: