Updates to DevTools in Chrome 62
developers.google.com
Updates to DevTools in Chrome 62
1–10 of 40 posts
Re: Updates to DevTools in Chrome 62
#2I see myself using the Block-level code coverage quite often.
Re: Updates to DevTools in Chrome 62
#3CMD+Shift+4 has always allowed you to take screenshots of any parts of your screen, (including your devtools), so curious why this is a feature in Chrome? Unless it's meant for Windows maybe where it's harder to take screenshots?
Re: Updates to DevTools in Chrome 62
#4CMD+Shift+4 has always allowed you to take screenshots of any parts of your screen, (including your devtools), so curious why this is a feature in Chrome? Unless it's meant for Windows maybe where it's harder to take screenshots?
You can hit printscreen in windows to take screenshots (1 key instead of 3, even easier than mac).
I could imagine it would be useful in remote debugging sessions (such as when inspecting android webviews over USB).
Re: Updates to DevTools in Chrome 62
#5CMD+Shift+4 has always allowed you to take screenshots of any parts of your screen, (including your devtools), so curious why this is a feature in Chrome? Unless it's meant for Windows maybe where it's harder to take screenshots?
You can hit printscreen in windows to take screenshots (1 key instead of 3, even easier than mac). I could imagine it would be useful in remote debugging sessions (such as when inspecting android webviews over USB).
Those are two totally different things. Windows take a screenshot of everything visible. Cmd+shift+4 on a Mac allows to select a region to save as a screenshot. Finally, if you are on Mac, this update provides node level acreenshot, allowing you to save an image of a HTML node with just one click, no need to drag the cursor. This is especially useful if the node takes more space than the viewport since before you had to stitch screenshots together.
Re: Updates to DevTools in Chrome 62
#6Earlier quoted context omitted.
You can hit printscreen in windows to take screenshots (1 key instead of 3, even easier than mac). I could imagine it would be useful in remote debugging sessions (such as when inspecting android webviews over USB).
Those are two totally different things. Windows take a screenshot of everything visible. Cmd+shift+4 on a Mac allows to select a region to save as a screenshot. Finally, if you are on Mac, this update provides node level acreenshot, allowing you to save an image of a HTML node with just one click, no need to drag the cursor. This is especially useful if the node takes more space than the viewport since before you had…
Agreeing on 100% of that. Just wanted to point out taking screenshots in windows isn't "harder". (You can also alt-prtscr for just the active window, or use the snipping tool to screenshot a region).
Re: Updates to DevTools in Chrome 62
#7CMD+Shift+4 has always allowed you to take screenshots of any parts of your screen, (including your devtools), so curious why this is a feature in Chrome? Unless it's meant for Windows maybe where it's harder to take screenshots?
I imagine this will be useful for taking screenshots of arbitrary elements via the headless mode.
Anyway, why would it be harder to take screenshots in Windows? Have they restricted the Win32 API recently (I haven't kept tabs)?
Re: Updates to DevTools in Chrome 62
#8Earlier quoted context omitted.
You can hit printscreen in windows to take screenshots (1 key instead of 3, even easier than mac). I could imagine it would be useful in remote debugging sessions (such as when inspecting android webviews over USB).
Those are two totally different things. Windows take a screenshot of everything visible. Cmd+shift+4 on a Mac allows to select a region to save as a screenshot. Finally, if you are on Mac, this update provides node level acreenshot, allowing you to save an image of a HTML node with just one click, no need to drag the cursor. This is especially useful if the node takes more space than the viewport since before you had…
> Windows take a screenshot of everything visible.
For the record, it's still not a region selector but there is also alt + printscreen to take only the visible windows.
Re: Updates to DevTools in Chrome 62
#9CMD+Shift+4 has always allowed you to take screenshots of any parts of your screen, (including your devtools), so curious why this is a feature in Chrome? Unless it's meant for Windows maybe where it's harder to take screenshots?
You can hit printscreen in windows to take screenshots (1 key instead of 3, even easier than mac). I could imagine it would be useful in remote debugging sessions (such as when inspecting android webviews over USB).
Don't you still have to open Paint, press paste, hit save, and choose where to save the screenshot?
For the record, cmd+shift+3 takes a screenshot and immediately saves it to your desktop on macOS.
Re: Updates to DevTools in Chrome 62
#10Earlier quoted context omitted.
Those are two totally different things. Windows take a screenshot of everything visible. Cmd+shift+4 on a Mac allows to select a region to save as a screenshot. Finally, if you are on Mac, this update provides node level acreenshot, allowing you to save an image of a HTML node with just one click, no need to drag the cursor. This is especially useful if the node takes more space than the viewport since before you had…
> Windows take a screenshot of everything visible. For the record, it's still not a region selector but there is also alt + printscreen to take only the visible windows.
There's also the built-in Snipping Tool, which allows you to take a screenshot of a selected region. I use it a lot at work.
Apparently, Windows 10 Creators Update comes with a shortcut to capture a region, Ctrl + Shift + S.
http://www.thewindowsclub.com/snipping-tool-capture-screensh...