Chrome Developer Tools
Chrome Dev Tools
There is not a particular reason why I chose Chrome Dev Tools over other browsers, other than that I use Chrome and Chrome Dev Tools more than other browsers. Chrome Dev Tools does offer a lot of useful features, some of which may apply to cutting-edge web development standards, that may not be present on other browsers.
Opening Chrome Dev Tools
Windows: F12 or Ctrl+Shift+I Linux: Ctrl+Shift+I Mac: Cmd+Opt+I
CDT and the DOM
DOM stands for Document Object Model. It’s a convention for representing and manipulating objects in HTML, XML, and XHTML documents (characterized by the angle brackets).
What can I do?
- Inspect any element
- View and change CSS rules
- View the element’s box model
There are several ways to select and inspect a particular element. One can:
Click on the element selection tool, then click on an element to jump to that position in the document.
Click on a specific element in the Dev Tools Elements view.
What Can I Do With These Elements?
Now that you have selected an element, you can right-click on the element to see some of the actions you can do:
Especially notable is the ability to toggle states such as active, hover, etc.
One of the most useful aspects of Dev Tools is the ability to change styles easily.
With an element selected, you can easily view its styles.
The “Styles” tab contains all of the CSS rules that govern the selected element.
We can see that the selected element has an id of “overlay”, and a class of “shell”, and that there are CSS rules defined for those selectors. The overridden styles are struck through. You can also toggle element state in this tab.
If you have animations or transitions with a timing function defined, you can also use the cubic bezier editor to help you with your animations.
The Computed Box Model provides the final computed values of margin, padding, width, height, etc. This is particularly useful when creating responsive layouts, or when there’s an awkward gap in your layout that you can’t find the source of. You can access this view by clicking on the computed tab.
Another very useful aspect of Dev Tools is the Network tab. This allows you to view all requests made from this webpage. This includes requests for images, files, fonts, scripts, etc.
It also helps you determine if there is a major bottleneck to page load times. In this image, try to find at least one request of each of the following types:
- HTML Document
Example Case Study
Cubemania is a Rubik’s Cube timing website that allows users to save their times. I use it a lot. Let’s analyze some of the requests it makes, specifically when a user logs in.
Now let’s open up Chrome Dev Tools and switch over to the Network Tab.
Make sure that the red “record” button in the top left is active.
Now I’ll click log in and see what requests are made.
We’re hit by a barrage of requests. Let’s look at the most interesting ones…
There’s a POST request at the very top. Usually these are for form submissions. Let’s click it open and take a more detailed look.
This a lot of information! We can deduce some things about how Cubemania works on the server side! For example, we now know that this POST request is making a call to the
http://www.cubemania.org/session endpoint, and that our session is stored in a
_Cubemania_session cookie. We can also see all of our request headers, which we might be able to use to recreate this request manually. If we scroll further down, we see the really interesting bit: the form data.
Now, I blacked out my password, of course, but as you can see, we know exactly what fields are passed into the POST request! Now, you might notice that there is also an
authenticity_token field. This is generated on the server side to try to make sure that you cannot spoof these requests. A bit of light Googling reveals that this is common in Ruby on Rails web apps. However, if we access the contents of the HTML first, we will be able to find the token and pass it into the POST request.
The resources tab contains information on the majority of client-side storage options. This includes local storage and cookies.
If we click open the local storage section, we can find that Cubemania stores all of my times in the local storage.
We can also view the cookies that Cubemania has stored. In here we do indeed see the
_Cubemania_session cookie we saw mentioned previously.
1) Go on the Cubemania website and answer these questions:
- Click on the ‘Users’ tab. What type of CSS selector is used to apply the yellow background on hover effect?
- Search for “naitian” in the search box. Monitor the network traffic. What is/are the query string parameter(s) of the search query? What is/are the value(s) of the parameter? Is this request a GET request or POST request? Why does that make sense?
2) Visit this wonderful lawn care website: http://kamronsoldozy.github.io
- Look in the Console. What are some errors? Are any of these errors related to each other?
- Based on these errors, what part of the home page is broken? What is it supposed to do?
- How can we fix this?
Bonus) Solve a Rubik’s cube in under 30 seconds.
Chrome Developer Tools has a lot more to offer than just what we covered here. If you’d like to find out more, here are some materials to keep you occupied.
GETrequest, There is no need for a
POSTrequest, since this value does not need to be kept confidential.
2a.) There are three errors. The failure to load
jquery.min.jsis directly tied to the
Uncaught ReferenceError: $ not defined.
2b.) By viewing the details of the
ReferenceError, we see that we need jQuery in image_slide.js, which is supposed to provide an image slider.
2c.) If we load in jQuery, the image slider should no longer be broken, and will alternate between the 2 images.