Issue metadata
Sign in to add a comment
|
Async stack traces are not being show for MutationObserver
Reported by
saideepa...@gmail.com,
Aug 29
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. Check the scenario mentioned in https://www.html5rocks.com/en/tutorials/developertools/async-call-stack/#toc-mutation-observer, this is no longer working. 2. You can use the example http://jsbin.com/tuwonefehi/edit?html,js,output What is the expected behavior? When paused on MutationObserver callback and with 'async stack traces enabled' devtools 'Call Stack' should show me all the async stack traces that led to MutationObserver callback. What went wrong? Currently its behaving as async stack traces is disabled for MutationObserver. Did this work before? Yes Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version:
,
Aug 30
Tried testing the issue on win-10 using chrome reported version #68.0.3440.106 and latest canary #70.0.3536.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to http://jsbin.com/tuwonefehi/edit?html,js,output. 2. Put a breakpoint in the code at sources but did not find the option for enabling async stack traces. reporter@ - Could you please check the attached screen cast and please let us know if anything missed from our end. Thanks...!!
,
Sep 3
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Aug 29