There is no separate TRACE log level for console.trace()
Reported by
nicky103...@gmail.com,
Sep 26
|
|||
Issue descriptionWhat is the expected result? I expect console.trace() log level to be different from any existing levels to be able to distinguish it in my code. What happens instead? As there is no LogSeverity constant for this, LOG_INFO is used instead.
,
Oct 3
This is done specifically in: https://cs.chromium.org/chromium/src/content/browser/frame_host/render_frame_host_impl.cc?sq=package:chromium&g=0&l=1510 Sending to devtools team to triage. But I think this is working as intended.
,
Oct 9
That's right, we have 4 levels: logging::LOG_VERBOSE - console.debug() logging::LOG_INFO - console.log() logging::LOG_WARNING - console.warn() logging::LOG_ERROR - console.error() I don't think we need a fifth logging level.
,
Oct 19
So maybe it is worth at least to make console.trace() produce LOG_VERBOSE, not LOG_INFO? |
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Sep 26