Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DomDistiller debug level is outputted into the console #4636

Open
MRVDH opened this issue May 29, 2019 · 12 comments
Open

DomDistiller debug level is outputted into the console #4636

MRVDH opened this issue May 29, 2019 · 12 comments

Comments

@MRVDH
Copy link

@MRVDH MRVDH commented May 29, 2019

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
@cherurg
Copy link

@cherurg cherurg commented Jun 4, 2019

Also, sometimes I get

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

when I use certain functions from rxjs.

@kaleazy
Copy link

@kaleazy kaleazy commented Jun 9, 2019

I second this, how do we remove?

@nikahmadz
Copy link

@nikahmadz nikahmadz commented Jul 4, 2019

It's annoying. should remove it

@MRVDH
Copy link
Author

@MRVDH MRVDH commented Jul 4, 2019

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.

@nikahmadz
Copy link

@nikahmadz nikahmadz commented Sep 5, 2019

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.

@louislefebvre
Copy link

@louislefebvre louislefebvre commented Nov 29, 2019

Hey, anything planned for this "issue" 😋 ?

@Coupz
Copy link

@Coupz Coupz commented Jan 20, 2020

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

@GMModded
Copy link

@GMModded GMModded commented Feb 2, 2020

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

@rafaelcastrocouto
Copy link

@rafaelcastrocouto rafaelcastrocouto commented Feb 24, 2020

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

@bsclifton
Copy link
Member

@bsclifton bsclifton commented Mar 2, 2020

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

@rafaelcastrocouto
Copy link

@rafaelcastrocouto rafaelcastrocouto commented Mar 2, 2020

Yes it still happens.
Untitled

@vdavid
Copy link

@vdavid vdavid commented Apr 6, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
10 participants
You can’t perform that action at this time.