Minimum DevTools Environment?

[camp...@gmail.com]

I'm interested in trying to fix some screen reader accessibility issues in developer tools, such as buttons which are announced by the JAWS screen reader as only "button", or "togglebutton".  I found the Devtools source on GitHub, whose README indicates the use of NPM.  The Contributing to Chrome DevTools guide seems to indicate installing Depot Tools and all of Chromium, about which I remember something about 100GB to install, and maybe Visual C++.  I found NPM with a Google search, but don't see any explicit mention of it as a requirement in the contribution guide or the README on GitHub.  What is the minimum setup I need to work on the DevTools front end?

I tried to follow the instructions in the Contribution guide for inspecting the inspector.  JAWS doesn't indicate the menu by which to undock DevTools, but I found a keystroke (Control+Shift+d) that is supposed to do that.  I executed the following:

Open a web page.

Press Control+Shift+i; devtools opens.

Control+Shift+d to undock; devtools appears to be in a separate tab.

Tab to elements tree.

Press Control+Shift+i;

Actual: Devtools closes.

Expected: Inspector opens inspecting the inspector.

What am I doing wrong?

I am using Google Chrome Version 65.0.3325.181 (Official Build) (64-bit) on Windows 10.

Thanks.

Gary

[Alexei Filippov]

Hi Gary,

You can try to run Canary with a custom build of DevTools frontend as described here: https://github.com/ChromeDevTools/devtools-frontend

-Alex

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/bf46462d-a1b5-46e6-8adc-d2b2ed2e34af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.