Chromium

This is a known issue and has been addressed already, the device should receive an update very soon.

This issue was migrated from crbug.com/chromium/1302699?no_tracker_redirect=1

[Monorail mergedinto: crbug.com/chromium/1299753]
[Monorail components added to Component Tags custom field.]

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

[Monorail components: -Platform>DevTools Platform>DevTools>JavaScript]

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

[Monorail components: Blink>JavaScript]

The class name is derived from the Symbol.toStringTag value, looked up on the prototype chain. Funnily enough that logic only pays attention to string data properties though, so it can be confused easily with add a getter.

One of the reasons why Symbol.toStringTag was added to ECMAScript was to have the ability to control the class name (sort of), so this seems to be working as intended.

For the record, Firefox seems to completely ignore the Symbol.toStringTag and always returns ArrayBuffer (consistently).

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8/+/b141fedfed575c2c600811811bcc4e09472eb975

commit b141fedfed575c2c600811811bcc4e09472eb975
Author: Benedikt Meurer <bmeurer@chromium.org>
Date: Tue Oct 19 10:43:32 2021

[inspector] Improve class name inference.

Previously having a `Symbol.toStringTag` property holding a string
somewhere in the prototype chain would always take predence over trying
to determine a reasonable name from the "constructor" (in case of
subclassing). This would lead to confusing behavior when diagnosing
objects in DevTools, for example

```js
class A extends URLSearchParams {};
new A()
```

would show `URLSearchParam` as class name for the instance rather than
`A`.

With this CL, we change the lookup logic to explicitly check for
`Symbol.toStringTag` and "constructor" along each step of the prototype
chain (skipping the "constructor" for the leaf object) and pick the
first one that yields a string (that is the function debug name in case
of "constructor").

Fixed: chromium:980018
Change-Id: Ic920b4bae02f965bc383c711f8de89c0de55fcac
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3231078
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Kim-Anh Tran <kimanh@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Kim-Anh Tran <kimanh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#77453}

[modify] https://crrev.com/b141fedfed575c2c600811811bcc4e09472eb975/src/objects/js-objects.cc
[add] https://crrev.com/b141fedfed575c2c600811811bcc4e09472eb975/test/inspector/regress/regress-crbug-980018.js
[add] https://crrev.com/b141fedfed575c2c600811811bcc4e09472eb975/test/inspector/regress/regress-crbug-980018-expected.txt

[Empty comment from Monorail migration]

This issue was migrated from crbug.com/chromium/980018?no_tracker_redirect=1

[Auto-CCs applied]
[Multiple monorail components: Blink>JavaScript, Platform>DevTools>JavaScript]
[Monorail components added to Component Tags custom field.]