 Ahoy there, here's what's new in DevTools in Chrome 81. First up, Device Mode now supports Moto G4. Click toggle device toolbar, then open the device list and select Moto G4. DevTools resizes the viewport to the dimensions of a Moto G4 device. Click more options, then select show device frame to show Moto G4 hardware around the viewport. Click the throttling list and select low-end mobile to throttle your network and CPU to more accurately simulate a typical mobile browsing experience. The cookies pane in the application panel now displays blocked cookies and lets you edit values. Here in this table, the blocked cookies have a yellow background and I can enable the only blocked checkbox to only show blocked cookies. To edit a value, double-click a cell. The only value that's not editable is the size column because that represents the network size of the cookie in bytes. The new copy as nojs fetch command lets you copy a fetch expression to the clipboard that includes cookie data. Right-click a network request and select copy copy as nojs fetch and DevTools copies a fetch expression to your clipboard. When I paste the expression into the console, you can see that the header's object contains a cookie field. To be honest, I don't know why the nojs command needs to include cookie data, but I'll find out and give an explanation in the comments section of this video. The manifest pane in the application panel now shows the exact same icon that Chrome uses. Previously, DevTools would perform its own network requests which would occasionally result in DevTools showing a slightly different icon than Chrome. You can now hover over CSS content properties to see unescaped values. After I right-click and inspect this node, I see the escape value of the content property in the styles pane. If I hover over that value, I see the unescape value. The console now provides more details on why a source map failed to load or parse. Previously, it would just log an error without explaining what went wrong. There's now a setting for disabling the default behavior of scrolling past the end of a file in the sources panel. Here in this file, when I scroll down, I can scroll well past the end of the file. To disable this default behavior, I press F1 and then disable the allow scrolling past end of file checkbox. Now, I can't scroll past the end of the file. Here's a bonus tip. DevTools has a lot of hidden features. An easy way to explore them is to press escape to open the drawer, then click more tools. Each of these options represents a tab with features. For example, search gives you a global search UI and quick sources is a way to view the source of a file while you've got another panel open. Thanks for watching. See you in six weeks for Chrome 82.