![]() ![]() Previously, hitting Enter resulted in adding new lines. Once you finish typing a live expression, you can click Enter to commit it. This change aligns the debugging behavior with other browsers like Firefox.Ĭhromium issues: 1014415, 1004038, 1112863, 1134899 # Console updates # Handle script execution errors in the ConsoleĮrrors during script evaluation in the Console now generate proper error events that trigger the window.onerror handler and are dispatched as "error" events on the window object.Ĭhromium issue: 1295750 # Commit live expression with Enter The Sources panel broke due to the endless loop.Ĭontinuing to execute JavaScript is causing a lot of trouble for developers and might leave the renderer in a broken state. The debugger now terminates script execution when reloading at breakpoint.įor example, the script got into an endless loop previously when setting and reloading at the ReactDOM breakpoint in this React demo. It is now blocked as you would expect (second screenshot).Ĭhromium issue: 833147 # Improved reloading at breakpoint However, when you opened the page via the Preview tab in the Network panel, the stylesheet was not blocked previously (hence the background turned into red). The browser blocked the stylesheet request by default. The page loads over a secure HTTPS connection, but the stylesheet loads over an insecure HTTP connection. Previously, it took more steps to emulate themes in the Rendering tab.Ĭhromium issue: 1314299 # Improved security on the Network Preview tabĭevTools now apply the Content Security Policy (CSP) in the Preview tab in the Network panel.įor example, the first screenshot shows a page that contains mixed content. You can now emulate the light and dark themes quicker (CSS media feature prefers-color-scheme) with the new shortcuts in the Styles pane. Our team is actively working on this feature and we are looking for your feedback for further enhancements.Ĭhromium issue: 1270700 # New shortcuts to emulate light and dark themes This is a preview feature to help web developers (especially non-performance experts) to identify and fix potential performance issues. Go to the Performance insights panel documentation to learn more with the step-by-step tutorial. Click on each insight item (for example, Render blocking request, layout shift) to understand the issue and potential fixes. Once the recording is complete, you get the performance insights on the Insights pane. For example, let’s measure the page load of this demo page. Open the panel and start a new recording based on your use case. Use the Performance insights panel to get actionable and use-case-driven insights on your website's performance. # Preview feature: New Performance insights panel ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |