Re: [Chrome DevTools] resources.pak

[Pavel Feldman]

1. Grab a build at http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html

2. Locate devtools_frontend.zip file located beside the build archive, extract it into a clean folder

3. Edit the styles (inspector.css or similar).

4. Start Chrome using --debug-devtools-frontend=<full path to extracted folder>

Happy hacking! Note that there are known issues with using devtools_frontend such as Heap Profiling and Pretty Print feature won't work. We are working on addressing those. Btw, if you come up with a convenient way of toggling the font size, please let us know and/or contribute your change into WebKit / Chromium. That way it gets into Chrome and you won't need to hack it again!

Regards

Pavel

[pe...@wisnovsky.net]

I can't believe that people have been asking for something so simple -- to be able to adjust the font size in dev tools -- for so long, but its only gotten harder rather than easier, since how you have to unpack a compressed directory tree to edit a file you shouldn't have to edit in the first place. This is nuts. Its more then nuts, its age discrimination: its saying if you too old to be able to read 7 point fonts any more you don't deserve to be using our tools. Its offensive, in fact.

[Mikhail Naganov]

Please look at this page to learn how you can tweak devtools:
http://code.google.com/chrome/devtools/docs/contributing.html

[pfeldman]

Please follow the bug http://code.google.com/p/chromium/issues/detail?id=10914
to track the progress on this issue.

[Peter Wisnovsky]

I found a better solution: run with a user CSS file and override it in the User.css file.

Your solution means that every time chrome gets upgrade you have to reunpack and reapply the change since its impossible to know if the binary has a dependency on resources.pak. Thats not really very convenient.

I notice that the user.css approach isn't in any of the top page of Google hits for "chrome dev tools font size too small".

Peter