This feature was introduced last year. You can enable it here: DevTools
->Settings
->General
->Console
->Hide network messages
.
See also Filtering the Console output and Additional settings in the devtools documentation.
More Related Contents:
- Why does Chrome debugger think closed local variable is undefined?
- How do you launch the JavaScript debugger in Google Chrome?
- Persistent Service Worker in Chrome Extension
- Allow Google Chrome to use XMLHttpRequest to load a URL from a local file
- Colors in JavaScript console
- Find out whether Chrome console is open
- Google Chrome console.log() inconsistency with objects and arrays
- $ Variable (Dollar Sign) in Chrome?
- How to disable JavaScript in Chrome Developer Tools?
- Javascript Debugging line by line using Google Chrome
- “Origin null is not allowed by Access-Control-Allow-Origin” in Chrome. Why? [duplicate]
- View list of all JavaScript variables in Google Chrome Console
- How do I send an HTTP GET request from a Chrome extension?
- how to set DOM Breakpoints in chrome
- What is the source of the double-dollar sign selector query function in Chrome/Firefox?
- How to get list of network requests done by HTML
- Is it possible for XHR HEAD requests to not follow redirects (301 302)
- Disable source maps in Chrome DevTools
- Cross-Origin XMLHttpRequest in chrome extensions
- How do I send an HTTP request from a Chrome extension?
- How to find what code is run by a button or element in Chrome using Developer Tools
- Chrome debugging – break on next click event
- What does the “System” category of records mean in Chrome Timeline profiling tool?
- Programmatically accessing function scope using Chrome DevTools console
- XmlHttpRequest.responseText while loading (readyState==3) in Chrome
- Cross-domain XMLHttpRequest using background pages
- Link to chrome:// url from a webpage
- Chrome developer tools do not show all JavaScript files any more
- Origin null is not allowed by Access-Control-Allow-Origin
- Phantom JS synchronous AJAX request : NETWORK_ERR: XMLHttpRequest Exception 101