I add --debug-devtools-frontend to Chromium but nothing changed!

[Jesse]

HI,All:
I am new to chrome and want to modify Chrome Developer Tools to meet
my need. My Chromium shortcut target is :E:\SOFT\webkit\chrome-
win32\chrome-win32\chrome.exe --debug-devtools-frontend=E:\SOFT\webkit
\devtools_frontend

When I start the Chromium,everything just as what it was.
I mean with or not with --debug-devtools-frontend, Chromium changed
nothing.

I download the chrome and devtools_frontend.zip at
http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Win/89207/

Can anyone tell me where is the problem?

Thanks very much.

[pfeldman]

> When I start the  Chromium,everything just as what it was.
> I mean with or not with  --debug-devtools-frontend, Chromium changed
> nothing.

... except for the devtools files are now taken from the E:\SOFT
\webkit
\devtools_frontend. You can locate devtools.html there along with a
bunch of JavaScript files and hack them. You can use devtools on
devtools to debug. Remember to use remote debugging to find out what
is wrong in case your edits kill devtools entirely (see
http://code.google.com/chrome/devtools/docs/contributing.html for more
details).

[Yura Y.]

Hi, i have the same situation, i run chrome with frontend debug args
and nothing happens. Built in devtools launched ( i did special marks
to distinguish them).
I use Goo Chrome version 12.0.742.122 and last build of devtools front
end.
Command line looks like this: C:\Users\UserName\AppData\Local\Google
\Chrome\Application\chrome.exe --debug-devtools-frontend=D:\projects
\mine\devtools

Any ideas?

Thanks.

[pfeldman]

You should only use devtools front-end build with Chromium from the
same build.

More details on why it fails for you: most likely Chrome is already
running with the same profile and instead of running the new one with
proper --debug-devtools-frontend flag, you get another window of
already running Chrome. To fix that, you should can add --user-data-
dir=<profile folder> to your command line. However, as I mentioned
above, only use front-end with Chromium from the same build. Otherwise
it may look like it is working, but you will hit random bugs due to
incompatibilities.

Pavel

[Yura Y.]

Thanks pfeldman. Now it works, but honestly, it is not obvious from
http://code.google.com/chrome/devtools/docs/contributing.html that
Chromium should be used. It is written that "Run Chrome with the
following command line flag: ..." and i thought that it is about
Google Chrome. So thank you again for enlightening me.

Cheers.