Sorry, missed a step after step 2. Load/open the index.html file you downloaded. Thanks much.

Judging by the source code Chrome only logs the first argument (m_message):
https://cs.chromium.org/chromium/src/v8/src/inspector/v8-console-message.cc?l=234&rcl=191c7ea0470d227ca56b0122c0992d9618832d3a
Can't it use V8ValueStringBuilder instead?

I am a novice to this codebase, but didn't understand how that is contributing to "log-files" only ? Where exactly logic is differing for writing to log file ? It writes properly to browser console output, just that it drops the arguments while writing to chrome_debug.log. Where is that happening ?

Do you plan to submit a patch?
That link shows that only m_message is sent to the frontend where file logging is handled afterwards via event subscription.
Browser console logging properly invokes V8ValueStringBuilder in V8ConsoleMessage::createForConsoleAPI.

I would love to submit the patch, let see see how soon I can do that. 

I am not sure that we would like to have this feature. We calculate message base on first argument and use it to dump message to terminal, for console inside DevTools we use more complicated logic which includes running special script which captures preview of the object. This preview requires some time and enabled only when DevTools is shown.

I am not sure I understand, ignoring second parameters onwards in a console.log() statement is a bug to me. We are not calculating message based on first argument.We are taking only the first argument, ignoring rest.

As workaround you can run following code before any JavaScript in the page:
let log = console.log;
console.log = function(...args) { for (let arg of args) { log(arg); }};

Message formatting code is located in v8-console.cc and v8-console-message.cc files inside V8, we send this message to blink at line: [1].

[1] https://cs.chromium.org/chromium/src/v8/src/inspector/v8-console-message.cc?rcl=336856688087b5b9c722526c5d9c730b6da6b295&l=418

@Reporter: Please check the issue as per comment#10 and let us know if this works for you. Hence adding Needs-Feedback label.

Thanks!

Yes, this will work. But why wouldn't you want this fixed ? I do not have bandwidth right now, otherwise I would be happy to fix it.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

--enable-logging is not an API that provides any guarantees regarding the console.log output. Please use remote debugging protocol for that.