Brave-browser: DomDistiller debug level is outputted into the console

Created on 29 May 2019  路  13Comments  路  Source: brave/brave-browser

Description

Console outputs DomDistiller debug level: 0 on all pages

Steps to Reproduce

  1. Navigate to any page.
  2. Open the dev console.

Actual result:

Console

Expected result:

No debug messages. This is an official build.

Brave version (brave://version info)

Version 0.64.77 Chromium: 74.0.3729.169 (Official Build) (64-bit)

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
    No
  • Does the issue resolve itself when disabling Brave Rewards?
    No
  • Is the issue reproducible on the latest version of Chrome?
    No
closeworks-for-me featurdev-tools prioritP5
Source
picture MRVDH
👍34

Most helpful comment

I don't understand why this has been labeled as priority/P5. As a web developer I use Brave to test and debug applications. It's annoying to keep seeing this message. Besides that, things like these should be in beta versions of Brave, not in public releases.

picture MRVDH on 4 Jul 2019
👍12

All 13 comments

Also, sometimes I get

VM77078:140 Exception happened in EmbedExtractors: (TypeError) : Cannot read property 'getAttribute' of null

when I use certain functions from rxjs.

cherurg picture cherurg on 4 Jun 2019

I second this, how do we remove?

kaleazy picture kaleazy on 9 Jun 2019
👍2

It's annoying. should remove it

nikahmadz picture nikahmadz on 4 Jul 2019
👍4

I don't understand why this has been labeled as priority/P5. As a web developer I use Brave to test and debug applications. It's annoying to keep seeing this message. Besides that, things like these should be in beta versions of Brave, not in public releases.

MRVDH picture MRVDH on 4 Jul 2019
👍12

Still at P5? and now came up a new annoying log on all page console.

[Deprecation] HTML Imports is deprecated and will be removed in M80, around February 2020. Please use ES modules instead. See https://www.chromestatus.com/features/5144752345317376 and https://developers.google.com/web/updates/2019/07/web-components-time-to-upgrade for more details.

nikahmadz picture nikahmadz on 5 Sep 2019

Hey, anything planned for this "issue" :yum: ?

louislefebvre picture louislefebvre on 29 Nov 2019

Bump, because this is also on production version with gridsome build on Netlify.

Coupz picture Coupz on 21 Jan 2020

Still an open issue..?
Would like to remove this debug message

iammati picture iammati on 2 Feb 2020

over a year ... time to "fix" this

rafaelcastrocouto picture rafaelcastrocouto on 24 Feb 2020
👍2

With latest version (1.4.95) which uses Chromium 80, I'm not seeing this anymore. I know it can be frustrating, but compared to the other backlog of issues this one didn't qualify as high priority (hence, labelled as P5)

@rafaelcastrocouto @GMModded @Coupz @louislefebvre can you update to latest and confirm if you see the issue? I've made sure to pick All levels in console and I'm not seeing it

bsclifton picture bsclifton on 2 Mar 2020

Yes it still happens.
Untitled

rafaelcastrocouto picture rafaelcastrocouto on 2 Mar 2020
👍1

I'm still seeing it.

Version 1.5.123 Chromium: 80.0.3987.163 (Official Build) (64-bit) (Windows 10)

And as a web developer, I find it rather annoying.

vdavid picture vdavid on 6 Apr 2020

Closing as I believe this is now fixed on all release channels (latest is on Chromium 84)

bsclifton picture bsclifton on 27 Jul 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

bsclifton picture bsclifton  路  3Comments
pitsi picture pitsi  路  3Comments
traffisco picture traffisco  路  3Comments
bbondy picture bbondy  路  3Comments
kerry-perret picture kerry-perret  路  3Comments