diff --git a/images/audits-panel.png b/images/audits-panel.png new file mode 100644 index 0000000..001da00 Binary files /dev/null and b/images/audits-panel.png differ diff --git a/images/image00.png b/images/chrome-devs-gplus.png old mode 100755 new mode 100644 similarity index 100% rename from images/image00.png rename to images/chrome-devs-gplus.png diff --git a/images/image02.png b/images/crbug.png old mode 100755 new mode 100644 similarity index 100% rename from images/image02.png rename to images/crbug.png diff --git a/images/devtools-window.png b/images/devtools-window.png index 19e76e0..dcc2282 100644 Binary files a/images/devtools-window.png and b/images/devtools-window.png differ diff --git a/images/image15.png b/images/discover-devtools-course.png similarity index 100% rename from images/image15.png rename to images/discover-devtools-course.png diff --git a/images/elements-panel.png b/images/elements-panel.png index a7cce65..c436fba 100644 Binary files a/images/elements-panel.png and b/images/elements-panel.png differ diff --git a/images/evalutate-expressions.png b/images/evalutate-expressions.png new file mode 100644 index 0000000..dcff039 Binary files /dev/null and b/images/evalutate-expressions.png differ diff --git a/images/javascript-debugging.png b/images/javascript-debugging.png index 9104eee..e4218e5 100644 Binary files a/images/javascript-debugging.png and b/images/javascript-debugging.png differ diff --git a/images/network-panel.png b/images/network-panel.png index 6f7e39a..e0628e0 100644 Binary files a/images/network-panel.png and b/images/network-panel.png differ diff --git a/images/profiles-panel.png b/images/profiles-panel.png index 0a4d991..c032a89 100644 Binary files a/images/profiles-panel.png and b/images/profiles-panel.png differ diff --git a/images/resources-panel.png b/images/resources-panel.png index 05d8333..46a0736 100644 Binary files a/images/resources-panel.png and b/images/resources-panel.png differ diff --git a/images/timeline-panel.png b/images/timeline-panel.png index fb7d6f5..ae77ba2 100644 Binary files a/images/timeline-panel.png and b/images/timeline-panel.png differ diff --git a/index.html b/index.html index a2cabb4..aadf491 100644 --- a/index.html +++ b/index.html @@ -2,22 +2,24 @@
The Chrome Developer Tools (DevTools for short), are a set web authoring and debugging tools -built into Google Chrome. The DevTools provide web developers deep access into the -internals of the browser and their web application. Use the DevTools to efficiently track down layout issues, set JavaScript breakpoints, and get insights for code optimization.
++ The Chrome Developer Tools (DevTools for short), are a set web authoring and debugging tools built into Google Chrome. + The DevTools provide web developers deep access into the internals of the browser and their web application. + Use the DevTools to efficiently track down layout issues, set JavaScript breakpoints, and get insights for code optimization. +
-Note: If you are a web developer and want to get the latest version of -DevTools, you should use Google Chrome Canary.
++ Note: If you are a web developer and want to get the latest version of DevTools, you should use Google Chrome Canary. +
-To access the DevTools, open a web page or web app in Google Chrome. Either:
The DevTools window will open at the bottom of your Chrome browser.
@@ -25,203 +27,261 @@ DevTools, you should use GooThere are several useful shortcuts for opening the DevTools:
For your day-to-day workflow, learning the shortcuts will save you time.
-For your day-to-day workflow, learning the -shortcuts will save you time.
The DevTools are organised into task-oriented groups in the toolbar at the top -of the window. Each toolbar item and corresponding panel let you work with a -specific type of page or app information, including DOM elements, resources, and -sources.
- - - -Overall, there are eight main groups of tools available view Developer Tools: -Elements, Resources, Network, Sources, Timeline, Profiles, Storage, Audits, and -Console. You can use the Ctrl+[ and Ctrl+] shortcuts to move -between panels.
- -The Elements panel lets you see -everything in one DOM tree, and allows inspection and on-the-fly editing of DOM -elements. You will often visit the Elements tabs when you need to identify the -HTML snippet for some aspect of the page. For example, you may be curious if an -image has an HTML id attribute, and what that attribute's value is.
- - - -Read more about inspecting the DOM and styles
- -The JavaScript Console provides two -primary functions for developers testing web pages and applications:
++ The DevTools are organised into task-oriented groups in the toolbar at the top of the window. + Each toolbar item and corresponding panel let you work with a specific type of page or app information, including DOM elements, resources, and sources. +
+ +Overall, there are eight main groups of tools available view Developer Tools:
You can use the Ctrl+[ and Ctrl+] shortcuts to move between panels.
++ The Elements panel lets you see everything in one DOM tree, and allows inspection and on-the-fly editing of DOM elements. + You will often visit the Elements tabs when you need to identify the HTML snippet for some aspect of the page. + For example, you may be curious if an image has an HTML id attribute and what the value is. +
+ + + +Read more about inspecting the DOM and styles
+ + +The JavaScript Console provides two primary functions for developers testing web pages and applications.
+ ++ It is a place to log diagnostic information using methods provided by the Console API. + Such as console.log() or console.profile(). +
++ A shell prompt where you can enter commands and interact with the document and the Chrome DevTools. + You can evaluate expressions directly in the Console, and can also use the methods provided by the Command Line API. + These include $() command for selecting elements, or profile() to start the CPU profiler. +
+ +Read more about working with the console
+As the complexity of JavaScript applications increase, developers need -powerful debugging tools to help quickly discover the cause of an issue and fix -it efficiently. The Chrome DevTools include a number of useful tools to help -make debugging JavaScript less painful.
++ As the complexity of JavaScript applications increase, developers need powerful debugging tools to help quickly discover the cause of an issue and fix it efficiently. + The Chrome DevTools include a number of useful tools to help make debugging JavaScript less painful. +
- - - +Read more about how to debug JavaScript with the DevTools »
+The Network panel provides insights into resources that are requested and -downloaded over the network in real time. Identifying and addressing those requests taking longer than expected is an essential step in optimizing your page.
++ The Network panel provides insights into resources that are requested and downloaded over the network in real time. + Identifying and addressing those requests taking longer than expected is an essential step in optimizing your page. +
- - - +Read more about how to improve your network performance »
+The Audit panel can analyze a page as it loads and provide suggestions and -optimizations for decreasing page load time and increase perceived (and real) -responsiveness. For further insight, we recommend also installing the PageSpeed extension.
++ The Audit panel can analyze a page as it loads. + Then provides suggestions and optimizations for decreasing page load time and increase perceived (and real) responsiveness. + For further insight, we recommend also installing the PageSpeed extension. +
+ +The Timeline panel gives you a complete overview of where time is spent when -loading and using your web app or page. All events, from loading resources to -parsing JavaScript, calculating styles, and repainting are plotted on a -timeline.
++ The Timeline panel gives you a complete overview of where time is spent when loading and using your web app or page. + All events, from loading resources to parsing JavaScript, calculating styles, and repainting are plotted on a timeline. +
- - - +Read more about how to improve rendering performance »
-The Profiles panel lets you profile the execution time and memory usage of a -web app or page. The Profiles panel includes a few profilers: a CPU -profiler, a JavaScript profiler and a Heap profiler. These help you to -understand where resources are being spent, and so help you to optimize your -code:
++ The Profiles panel lets you profile the execution time and memory usage of a web app or page. + These help you to understand where resources are being spent, and so help you to optimize your code. + The provided profilers are: +
Read more about using how to improve JavaScript and CSS performance »
+The Resources panel lets you inspect resources that are loaded in the -inspected page. It lets you interact with HTML 5 Database, Local Storage, -Cookies, AppCache, etc.
++ The Resources panel lets you inspect resources that are loaded in the inspected page. + It lets you interact with HTML5 Database, Local Storage, Cookies, AppCache, etc. +
- - - +Read more about inspecting storage resources »
There are several other areas of the DevTools documentation that you might find of benefit to review. -These include:
+There are several other areas of the DevTools documentation that you might find of benefit to review. These include:
Want more tips on DevTools? Watch our regular show The -Breakpoint -on YouTube.
- - -You can also follow us on @ChromiumDev or ask a question using the forums.
- +or checkout the Google Chrome Developers page on -Google+.
+Be sure to checkout the Google Chrome Developers page on Google+.
+ +Explore and master the DevTools with our free "Discover DevTools" course on Code School.
- +To submit a bug or a feature request on DevTools, please use issue tracker at -http://crbug.com. Please also mention "DevTools" in the bug -summary.
++ To submit a bug or a feature request on DevTools, please use issue tracker at http://crbug.com. + Please also mention "DevTools" in the bug summary. +
- +Anyone can also help make the DevTools better be directly -contributing back to the source.
+Anyone can also help make the DevTools better be directly contributing back to the source.
-Looking to use the DevTools to debug Chrome extensions? Watch Developing and -Debugging extensions or read the -Debugging -tutorial.
++ Looking to use the DevTools to debug Chrome extensions? Watch Developing and Debugging extensions. + A Debugging tutorial is also available. +
{{/partials.standard_devtools_article}}