Brave-browser: Misleading childNodes logging behaviour

Created on 6 Feb 2020 · 4Comments · Source: brave/brave-browser

Description

Brave logs a misleading message on devtools. NodeList has [div] inside but length is 0 and doesn't have anything inside the array. I don't know if this is a default common behaviour or not but this is really confusing to me.

Steps to Reproduce

I opened index.html with the following code on Brave:

<html>
  <body>
     <div id="list"></div>
     <script>
        const list = document.getElementById("list");
        const node = document.createElement("div");

        list.appendChild(node);
        console.log(list.childNodes);
        list.removeChild(node);
      </script>
  </body>
</html>

Open devtools console.

Actual result:

Provided on Description section.

Expected result:

NodeList array to have div element inside and length being 1.

Reproduces how often:

Easily reproduced.

Brave version (brave://version info)

Brave: 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)
Revision: 021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}
OS: Windows 10 OS Version 1903 (Build 18362.592)

Version/Channel Information:

Can you reproduce this issue with the current release?
Can you reproduce this issue with the beta channel? Yes.
Can you reproduce this issue with the dev channel? Yes.
Can you reproduce this issue with the nightly channel? Yes.

Other Additional Information:

Does the issue resolve itself when disabling Brave Shields? NA.
Does the issue resolve itself when disabling Brave Rewards? NA.
Is the issue reproducible on the latest version of Chrome? Yes.

Miscellaneous Information:

Chromiuwaiting upstream featurdev-tools repros-on-chrome

Source

ABCbum

All 4 comments

@ABCbum Is this still an issue on 1.5.115? We've had quite a few chromium updates since then.

rebron on 27 Mar 2020

👍1

Hi @rebron , i can confirm that this is still an issue in current version (Version 1.5.115 Chromium: 80.0.3987.149 (Official Build) (64-bit)). It is fine with the initial load but if i reload then the bug still comes back.

Thanks!!

ABCbum on 28 Mar 2020

Is the issue reproducible on the latest version of Chrome? Yes.

@ABCbum assuming it's still an issue in the last Chrome as well? Sounds like you also reproduced it on Chrome originally as per the above.

kjozwiak on 28 Mar 2020

👍1

@ABCbum assuming it's still an issue in the last Chrome as well?

@kjozwiak , yes i can reproduce it on Chrome (Version 81.0.4044.83 (Official Build) beta (64-bit)) the behaviour is exactly the same, fine with the initial load but reload then it's wrong. Thanks!

ABCbum on 29 Mar 2020

👍1

Was this page helpful?

0 / 5 - 0 ratings