$ uses the querySelector DOM method, which returns a single matching DOM element, while $$ uses querySelectorAll, which returns an array of all matching elements. Routine 2: From the console panel, use either the $('selector') or $$('selector') console commands to select element(s) from the DOM. Enter a CSS selector into the search input UI. Routine 1: From the elements panel, use a keyboard shortcut (win: Ctrl+f, mac: Cmd+f) to open up the search input UI. You want to locate a node element(s) in the DOM using a CSS selector. Click the element you want to view and it will become selected in the elements panel for further investigation. Then use the mouse to hover over elements on the page. Routine: From the elements panel, click on the magnify icon. You want to select a DOM node in the elements panel visually using the mouse pointer. Enter any text you'd like to be found in the current source file (Note: to un-minify the source click on the icon). Routine: From the source panel, select and open a source file, then use a keyboard shortcut (win: Ctrl+f, mac: Cmd+f) to open up the search input UI. You want to perform a text string search on an individual source file. Note that clicking on one of the results (line number from source) will open the source in the source panel. Enter any text you'd like to be found within the current HTML page. Routine: From any panel use a keyboard shortcut (win: Ctrl+Shift+f, mac: Cmd+Opt+f) to open up the search panel. You want to perform a text string search across all of the text contained within all of the source files used by the current HTML page. Enter any text you'd like to be found on the current HTML page. Routine: From the elements panel, use a keyboard shortcut (win: Ctrl+f, mac: Cmd+f) to open up the search input UI. You want to perform a text string search on the current HTML page. Below, you will find 16 short videos detailing solutions to the most common search-find-edit routines using Chrome DevTools. In this article, I'm going to help myself, and hopefully you the reader, gain a robust understanding of finding things and doing things using Chrome DevTools. The problem is that I haven't taken the time to learn the fundamentals well enough to remember the basic routines of search-find-edit in-between DevTools uses. I consistently fumble my way through the searching, finding, and editing UI options in the Chrome Developer Tools (aka Chrome DevTools).
0 kommentar(er)
