Unable to get standalone devtools working on recent revisions

[Hans Nielsen]

TL;DR: running the Chrome devtools front-end from the standalone repo doesn't work anymore. Is this a bug?

I attempted to do some devtools front-end hacking (without compiling all of Chromium) based on these instructions on how to work on the devtools:

https://docs.google.com/document/d/1WNF-KqRSzPLUUfZqQG5AFeU_Ll8TfWYcJasa_XGf7ro/

I started by checking out the devtools repo from here (revision 536c06b4):

https://chromium.googlesource.com/chromium/src/third_party/WebKit/Source/devtools/

I started a recent Chromium checkout with remote debugging enabled on port 9222. I then started a local webserver (on port 9999) in the devtools directory. I navigated to "localhost:9222/#http://localhost:9999/front_end/inspector.html" and selected a page, bringing me to "http://localhost:9999/front_end/inspector.html?ws=...".

The inspector did not appear. I looked at the console and noted that there were several 404 errors: "/front_end/InspectorBackendCommands.js", "/inspector.json", and "/front_end/SupportedCSSProperties.js".

I then did a full Chromium checkout (revision 400593) using "fetch --nohooks --no-history chromium" and encountered the same result.

I ran "git bisect" against the devtools repo and found that commit b9ff6c43 appears to have broken the existing directions (the previous commit lets the devtools load successfully).

For completeness, I did a full Chromium build with "debug_devtools=1" and it works as expected.

Is there going to be a new way to work on the devtools without doing the full Chromium compile (or is this behavior a bug)? Now that I'm set up with the Chromium build (which took six hours :P) it's not a big deal, but it would be nice to have the option.

Thanks!

Hans

[Athyuttam Reddy]

I'm facing the same issue. After building Chromium were you able to use the server method? Or did you have to build after each edit you made to the devtools codebase?

[Athyuttam Reddy]

This gist might help for now, I'm building at the moment: https://gist.github.com/paulirish/2d84a6db1b41b4020685

On Monday, June 20, 2016 at 10:47:09 PM UTC-7, Hans Nielsen wrote:

[Andrey Lushnikov]

Thanks for the heads-up, the bug has been filed: https://crbug.com/623602

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/d2572af1-007b-41f8-a5cd-5653a17f02c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hans Nielsen]

Thanks for filing the bug!

Athyuttam: I also used that gist to get started. With "debug_devtools=1" you can just edit the JS files directly in the Chromium tree that you checked out: https://gist.github.com/paulirish/2d84a6db1b41b4020685#devtools-debugging

Hans

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[Athyuttam Reddy]

Thanks for filing the bug! 

Also thanks Hans! I got it working with debug_devtools=1, although I had to adapt it to GN, the new build system: https://chromium.googlesource.com/chromium/src/+/master/tools/gn/docs/cookbook.md.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/d2572af1-007b-41f8-a5cd-5653a17f02c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-chrome-developer-tools/sP1J63c636Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/4ce72e32-fded-4e57-ad2a-5cef606ab0bd%40googlegroups.com.