【外部リンク】
https://docs.microsoft.com/ja-jp/microsoft-edge/devtools-guide
Microsoft Edge Developer Tools
2018/10/02
読了までの所要時間: 3 分
共同作成者
Erika Doyle Navara Mohit gauniyal Libby McCormick Zoher Ghadyali
この記事の内容
Core tools
Microsoft Store app
Feedback
General Shortcuts
The Microsoft Edge DevTools are built with TypeScript, powered by open source, optimized for modern front-end workflows, and now available as a standalone Windows 10 app in the Microsoft Store!
For more on the latest features, check out DevTools in the latest update of Windows 10 (EdgeHTML 18).
Core tools
Microsoft Edge DevTools
The Microsoft Edge DevTools include:
An Elements panel to edit HTML and CSS, inspect accessibility properties, view event listeners, and set DOM mutation breakpoints
A Console to view and filter log messages, inspect JavaScript objects and DOM nodes, and run JavaScript in the context of the selected window or frame
A Debugger to step through code, set watches and breakpoints, live edit your code, and inspect your web storage and cookie caches
A Network panel to monitor and inspect requests and responses from the network and browser cache
A Performance panel to profile the time and system resources required by your site
A Memory panel to measure your use of memory resources and compare heap snapshots at different states of code execution
A Storage panel for inspecting and managing your web storage, IndexedDB, cookies and cache data
A Service Workers panel for managing and debugging your service workers
An Emulation panel to test your site with different browser profiles, screen resolutions, and GPS location coordinates
Please keep sending your feedback and feature requests!
ヒント
Test on Microsoft Edge free from any browser: We partnered with BrowserStack to provide free live and automated testing on Microsoft Edge.
Microsoft Store app
The Microsoft Edge DevTools are now available as a standalone Windows 10 app from the Microsoft Store, in addition to the in-browser (F12) tooling experience. With the store version comes a chooser panel for attaching to open local and remote page targets and a tabbed layout for easy switching between DevTools instances.
Local debugging
To debug a page locally, simply launch the Microsoft Edge DevTools app. The Local panel of the chooser will display all of the active EdgeHTML content processes, including open Edge browser tabs, running PWAs (WWAHost.exe processes), and webview controls. Click on your desired target to attach and open a new tab instance of the DevTools.
DevTools app Local panel
Remote debugging
The Microsoft Edge DevTools app introduces basic support for debugging pages on a remote machine via our newly released DevTools Protocol. With the latest release comes remote access to core functionality in the Debugger, Elements (for read-only operations), and Console panels. Remote debugging is limited to Microsoft Edge running desktop hosts, with support for other EdgeHTML hosts and Windows 10 devices coming in future releases.
To get started, check out the Microsoft Edge DevTools section of the DevTools Protocol docs.
DevTools app Remote panel
Feedback
Please send us your feedback so we can continue improving the Microsoft Edge DevTools for you! Simply open the tools (F12) and click the Send feedback button.
You can also add and upvote tooling requests to our UserVoice forum and become a Windows Insider to preview the latest features coming to the DevTools. Use the Windows Feedback Hub app to post, upvote, track and get support for general Windows suggestions and problems.
General Shortcuts
These shortcuts control the main DevTools window and/or work across all tools.
Action Shortcut
Show/Hide DevTools (opens to last viewed panel) F12, Ctrl+Shift+I
Toggle docking (Undock/Bottom/Right) Ctrl+Shift+D
Show non-editable HTML source code in Debugger Ctrl+U
Show/hide Console at the bottom of any other tool Ctrl+`
Switch to Elements (DOM Explorer) Ctrl+1
Switch to Console Ctrl+2
Switch to Debugger Ctrl+3
Switch to Network Ctrl+4
Switch to Performance Ctrl+5
Switch to Memory Ctrl+6
Switch to Emulation Ctrl+7
Help Document F1
Next tool Ctrl+F6
Previous tool Ctrl+Shift+F6
Previous tool (from history) Ctrl+Shift+[
Next tool (from history) Ctrl+Shift+]
Next Subframe F6
Previous Subframe Shift+F6
Next match in Search box F3
Previous match in Search box Shift+F3
Find in search box Ctrl+F
Give focus to console at the bottom Alt+Shift+I
Dock/undock tools (toggle docking) Ctrl+P
Launch DevTools to Console Ctrl+Shift+J
Refresh the page. Note: if you're debugging and paused at a breakpoint, this resumes execution first. Ctrl+Shift+F5 or Ctrl+R
--
注目の投稿
【Windowsエラーログ】メッセージとエラーコードの早見表
【Windowsエラーログ】メッセージとエラーコードの早見表 イベントビューアーに記録されたエラーの簡易リファレンスです。 DefenderApiLogger の最大サイズ超過 (エラーコード: 0xC0000035) 状況: Windows Defenderのログバッファ(バッ...
人気の投稿
-
【現象】 以下の現象が発生しました 手順が正しくないか、申込操作の有効期限が過ぎております。 お手数をお掛けしますが、最初からお手続きください。 このページが表示される主な理由は以下の通りとなります。 ※複数のブラウザ、タブ、端末を使用した場合 ※操作途中で画面...
-
n117 データアクセスに制限がかかっています PS Vita エラーコード「N117」の解説:データアクセス制限の原因と解決策 PS Vitaを使用中に突然表示される「N117(データアクセスに制限がかかっています)」というエラー。これは主に、ネットワーク通信やPlay...
-
PS Vita / PS Vita TV のエラーコード PS Vita / PS Vita TV エラーコード完全ガイド:原因と解決策まとめ 1. ネットワーク・接続関連のエラー もっとも多いのが、PlayStation™Network(PSN)への接続や通信に関するエラー...
-
エラーコード 2.1.1 HRESULT Values 0x80040905 【外部リンク】 https://msdn.microsoft.com/en-us/library/cc704587.aspx Combining the fields of a...
-
【外部リンク】 https://support.nintendo.co.jp/app/answers/list/search/1/kw/%E3%82%A8%E3%83%A9%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89/search/1/p/8664...