UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.189 Safari/537.36 Vivaldi/1.95.1077.55

Steps to reproduce the problem:
When logging an object, it shows __proto__ as part of the properties of the object

What is the expected behavior?
It should highlight the fact that the prototype link is special and not a normal property. It should use a syntax similar to function objects, which already have things like [[FunctionLocation]] and [[Scopes]]. It should should follow the ECMAScript spec convention of denoting internal slots with double brackets.

What went wrong?
__proto__ is deprecated and should not be used any more in any code (the replacements Object.getPrototypeOf/setPrototypeOf work much better). __proto__ is just an inherited getter/setter, but seeing it in the devtools is very confusing. Especially for new developers, it leads to a misguided understanding, thinking that __proto__ is an own property of every object that will be used for looking up inherited properties. They continue to use it in their own code to access (and sometimes even change) the prototype chain, not being aware that they use a deprecated web-legacy feature.

Did this work before? No 

Chrome version: 64.0.3282.189  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

(I love the change from "undefined" to "empty" for array slots <https://bugs.chromium.org/p/chromium/issues/detail?id=732021> :D)