Investigate displaying property from prototype at the same level as own properties
Categories
(DevTools :: Shared Components, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: jakub.g.opensource, Unassigned)
Details
(Keywords: parity-chrome)
Attachments
(1 file)
|
45.97 KB,
image/png
|
Details |
PerformanceNavigationTimingPrototype.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Log in console, observe value is true:
secureConnectionStart in PerformanceNavigationTiming.prototype
Log in console, observe that secureConnectionStart is not there:
PerformanceNavigationTiming.prototype
Actual results:
PerformanceNavigationTiming.prototype does not show all keys on the prototype
Expected results:
PerformanceNavigationTiming.prototype should show all keys in the prototype
What actually happens is that secureConnectionStart is inherited from __proto__ and if you expand <prototype> you will see it.
In a way, this is a "more correct" behavior than what Chrome does, which is to display all parent proto props on top level.
But it's somehow confusing compared to the output of "fieldname" in Something.prototype.
Feel free to close this bug if it's intentional.
|
||
Updated•5 years ago
|
|
||
Updated•10 months ago
|
Description
•