Issue metadata
Sign in to add a comment
|
Blackboxing formatted script will result in blackboxing the formatted script instead of the unformatted one
Reported by
labobol...@gmail.com,
Nov 30 2016
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
Steps to reproduce the problem:
1.
Cause a breakpoint in a minimized script. Easiest way is to find a site using disqus. Go to dev tools, tab Source and press the pause script button.
2.
Move the mouse cursor over the disqus iframe. Script execution should pause.
3.
In dev tools click 'Pretty print' {} button.
4.
Right click callstack -> Blackbox script.
What is the expected behavior?
The blackboxed script should be:
/common\.bundle\.b02a4f1e88aff9cf3af5e60c73ab15cc\.js$
What went wrong?
The blackboxed script is:
/common\.bundle\.b02a4f1e88aff9cf3af5e60c73ab15cc\.js:formatted$
Did this work before? N/A
Chrome version: 54.0.2840.99 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
If this isn't a bug than the bug is that the blackboxing doesn't work.
Since it will still pause in script:
/common\.bundle\.b02a4f1e88aff9cf3af5e60c73ab15cc\.js$
Instead of knowing that the unformatted script and the formatted script is connected and that the unformatted script should be skipped over because of blackboxing.
,
Nov 30 2016
,
Oct 16 2017
,
Jan 3 2018
Requires help from DevTools frontend guru: Andrey. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Nov 30 2016Labels: M-54