DevTools: breakpoint paused in another thread (e.g. ServiceWorker) doesn't look active
Reported by
kenneth....@gmail.com,
Nov 14 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Load mobile.twitter.com 2. Open serviceworker/main.js in devtools 3. Set breakpoint in handleFetchAsset 4. Clear serviceworker & caches, refresh 5. Spinner shows, breakpoint appears inactive. What is the expected behavior? 5. Spinner shows, breakpoint should be focused. What went wrong? I needed to choose the serviceworker thread in the devtools pane to see which breakpoint was active. There's no visual indication that this is so, so I was assuming Chrome was hanging. Either focusing the correct thread (best) or providing a visual clue that I should do so, would be very helpful. Did this work before? N/A Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Nov 15 2017
Thanks for the report. I'm able to reproduce the behavior after I switch to the 'Main' thread and refresh. We could solve this with some better UX. Currently a paused breakpoint has a lighter blue background on the entire line. Perhaps we could show some sort of lighter gray background on the entire line, when it is being actively paused, but on a different thread. kozy@, wdyt?
,
Nov 15 2017
,
Dec 8 2017
,
Dec 13 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by manoranj...@chromium.org
, Nov 14 2017