Bug 288605 – `toString` method of `obj` is triggered by `console.log(obj)`

• Status: NEW
• Component: Web Inspector

[Joe]

Developers expect `console.log` to be minimally disruptive - i.e. simply log the arguments and nothing else. In some cases it is actually invalid to call `toString` on certain objects, and yet the developer stills wants to be able to log the object so they can inspect it in the console with the interactive object explorer. In other words, `toString` should be considered user-land, not for developer tools to use.
```js
let a = {};
a.toString = function() { console.log("toString() called!"); return "123"; }
console.log(a); // only in Safari this triggers the "toString() called!" to be logged
```
It would be great if WebKit could become compatible with other browsers on this issue.

[Radar WebKit Bug Importer]

<rdar://problem/145739490>

[Razvan Caliman]

Breadcrumbs for investigation:

WI.RuntimeManager.evaluateInInspectedWindow()
----- inspector protocol -----
- PageRuntimeAgent::evaluate() --> gets or creates InjectedScript via PageRuntimeAgent::injectedScriptForEval()
  - InspectorRuntimeAgent::evaluate()
    - InjectedScript::evaluate() --> creates ScriptFunctionCall
      -  InjectedScriptBase::makeEvalCall()
        - InjectedScriptBase::makeCall()
          - InjectedScriptBase::toInspectorValue() --> using result from ScriptFunctionCall::call()