console.error only logs first arguments after Chrome upgraded to 49.0.2623.110 m
Reported by
zhaoyu0...@gmail.com,
Apr 6 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Steps to reproduce the problem: 1. Execute console.error(1,2,3); What is the expected behavior? Output 1 2 3 What went wrong? Output 1 Did this work before? N/A Chrome version: 49.0.2623.110 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0 console.log(1,2,3); // log 1 2 3 console.warn(1,2,3); // log 1 2 3 console.error(1,2,3); // log 1
,
Apr 7 2016
,
Apr 8 2016
May I suggest to increase the issue priority? This is a feature broken. Console.error should support pass in a list of parameters. expected: console.error(object [, object, …]); https://developers.google.com/web/tools/chrome-devtools/debug/console/console-reference?hl=en#error https://developer.mozilla.org/en-US/docs/Web/API/Console/error
,
Apr 10 2016
,
Apr 11 2016
Thanks l446240525@gmail.com. I verified again, found this bug is caused by javascript-errors-notifie extension. https://chrome.google.com/webstore/detail/javascript-errors-notifie/jafmfknfnkoekkdocjiaipcnmkklaajd console.error works well after I disabled that extension. Thanks again.
,
Apr 11 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by zhaoyu0...@gmail.com
, Apr 6 201638.7 KB
38.7 KB View Download