--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/e36ca2b3-9245-490b-aadc-0a5f2be95101%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/ac2cbdaf-22ef-4a63-b52f-9952d855acc7%40googlegroups.com.
1., 2. Look under the Workers in the Sources panel sidebar. (See the bottom of the attached screenshot)3. http://www.html5rocks.com/en/tutorials/developertools/revolutions2013/#toc-workspaces
On Mon, Apr 7, 2014 at 5:07 PM, <da...@windward.net> wrote:
Hi;How exactly do I:
- open it by clicking a link in the workers list in Sources panel sidebar
- check a checkbox that makes all workers break on start.
- (add a local folder and) map it to the network resources
I tried to find the first 2 items and could not. I did find how to add a local folder, but could not find how to map it.??? - thanks - dave
On Monday, April 7, 2014 3:05:27 AM UTC-6, Vsevolod Vlasov wrote:Workers debugging could only be done in a separate worker front-end currently. You could open it by clicking a link in the workers list in Sources panel sidebar. You could also check a checkbox that makes all workers break on start.As for debugging the scripts that are loaded dynamically you have two options:1) Wait until the script is loaded, set the breakpoint and reload the page. the breakpoint will be kept in the VM and debugger will pause on it when needed.2) Use DevTools workspaces to add a local folder and map it to the network resources so that the dynamically loaded script file is always available and you could set breakpoint in it.On Thu, Apr 3, 2014 at 8:38 PM, <da...@windward.net> wrote:Hi;The Sources tree does not list all files, just the ones it knows are in use. How can I get other files in there so I can set breakpoints in them before they execute for the first time?Also, how do I get worker .js files in the Sources? Generally they don't show and Ctrl-O doesn't list it. (And sometimes they do show up - no idea why when that happens.)
--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/99f92158-58e5-4d3b-bc8a-1b91ff7031a1%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
1., 2. Look under the Workers in the Sources panel sidebar. (See the bottom of the attached screenshot)3. http://www.html5rocks.com/en/tutorials/developertools/revolutions2013/#toc-workspaces
On Mon, Apr 7, 2014 at 5:07 PM, <da...@windward.net> wrote:
Hi;How exactly do I:
- open it by clicking a link in the workers list in Sources panel sidebar
- check a checkbox that makes all workers break on start.
- (add a local folder and) map it to the network resources
I tried to find the first 2 items and could not. I did find how to add a local folder, but could not find how to map it.??? - thanks - dave
On Monday, April 7, 2014 3:05:27 AM UTC-6, Vsevolod Vlasov wrote:Workers debugging could only be done in a separate worker front-end currently. You could open it by clicking a link in the workers list in Sources panel sidebar. You could also check a checkbox that makes all workers break on start.As for debugging the scripts that are loaded dynamically you have two options:1) Wait until the script is loaded, set the breakpoint and reload the page. the breakpoint will be kept in the VM and debugger will pause on it when needed.2) Use DevTools workspaces to add a local folder and map it to the network resources so that the dynamically loaded script file is always available and you could set breakpoint in it.On Thu, Apr 3, 2014 at 8:38 PM, <da...@windward.net> wrote:Hi;The Sources tree does not list all files, just the ones it knows are in use. How can I get other files in there so I can set breakpoints in them before they execute for the first time?Also, how do I get worker .js files in the Sources? Generally they don't show and Ctrl-O doesn't list it. (And sometimes they do show up - no idea why when that happens.)
--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.