Warnings in the console lack backtrace
Reported by
teo8...@gmail.com,
Apr 22 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36 Steps to reproduce the problem: 1. Do something that produces a warning, such as a synchronous XMLHttpRequest which triggers this warning: "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience." or trying to get location on a non-secure origin, or whatever generates warnings What is the expected behavior? The warning should appear in the console with a clickable dropdown allowing you to see the full backtrace, just like with errors What went wrong? The warning is displayed in the console, but only with the file and line number (and link to see the source) of the exact point where the warning was triggered. There's no trace. There's just no good reason for that. It's as important to be able to trace a warning as it is to trace an error. Did this work before? No Chrome version: 50.0.2661.86 Channel: stable OS Version: Flash Version: Shockwave Flash 21.0 r0
,
Jul 19 2016
,
Jul 29 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/17575d9fed8e88bbc74c926e6dd037681b062b1e commit 17575d9fed8e88bbc74c926e6dd037681b062b1e Author: kozyatinskiy <kozyatinskiy@chromium.org> Date: Fri Jul 29 01:18:57 2016 [DevTools] Show stack for console.warn messages BUG= 605932 R=luoe@chromium.org,lushnikov@chromium.org Review-Url: https://codereview.chromium.org/2189223002 Cr-Commit-Position: refs/heads/master@{#408545} [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/http/tests/inspector/console-resource-errors-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/http/tests/inspector/console-xhr-logging-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/inspector/console-document-write-from-external-script-logging-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/inspector/console/console-filter-level-test-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/inspector/console/console-log-before-inspector-open-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/inspector/console/console-log-without-console-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/LayoutTests/inspector/console/console-tests-expected.txt [modify] https://crrev.com/17575d9fed8e88bbc74c926e6dd037681b062b1e/third_party/WebKit/Source/devtools/front_end/console/ConsoleViewMessage.js
,
Jul 29 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by allada@chromium.org
, Apr 25 2016Status: Available (was: Unconfirmed)