News for hackers. Stuff that matters.
Re:Google Code Blog: Chrome Extensions for Web Development by aboodman on Tuesday June 01, 2010 @11:35AM (#1395288)
Omnibus-response to previous comments:

- The ability to intercept and modify requests is indeed missing. We've had some proposals for how to add that to our APIs, but nothing concrete yet.

- We're working on the ability to manipulate the cookie store: http://src.chromium.org/cgi-bin/gitweb.cgi?p=chromium.git;a=...

- The browser cache isn't something we've ever even thought about before. Thanks for bringing it up.

Re:Google Code Blog: Chrome Extensions for Web Development by esers on Tuesday June 01, 2010 @09:27AM (#1394968)
There doesn't seem to be a Chrome equivalent to "Live HTTP Headers" for Firefox.

Viewing, logging, replaying, and manipulating HTTP headers is an absolute _must_ for many web developers.

Wireshark is fantastic, but having this feature embedded in the browser is very useful.

Re:Google Code Blog: Chrome Extensions for Web Development by johnswamps on Tuesday June 01, 2010 @01:22PM (#1395557)
It would be great, but the API support is not there, which is why there aren't any extensions to spoof your user-agent either. Compared to Firefox extensions (which basically let you do everything), Chrome extensions are much more fine-grained and can only use APIs specifically designed for use with extensions. There are several features that Chrome extensions developers have been requesting, such as this and the ability to prevent elements from being loaded (which is why there is no noscript and all the ad blockers are only half-baked solutions)
Re:Google Code Blog: Chrome Extensions for Web Development by enomar on Tuesday June 01, 2010 @11:48AM (#1395329)
The resources tab in the developer tools is a good start. But I'd love to see the ability in the extensions API to inspect (and manipulate) the HTTP stream.
Re:Google Code Blog: Chrome Extensions for Web Development by chasingsparks on Tuesday June 01, 2010 @12:41PM (#1395461)
I'm happy to see Chris Pederick's Web Developer has been ported.

https://chrome.google.com/extensions/detail/bfbameneiokkgbdm...

Re:Google Code Blog: Chrome Extensions for Web Development by lftl on Tuesday June 01, 2010 @03:07PM (#1395851)
It's missing a ton of the functionality from the FF version where Chrome doesn't offer comparable APIs.
Re:Google Code Blog: Chrome Extensions for Web Development by mrinterweb on Tuesday June 01, 2010 @12:32PM (#1395439)
Firebug has set the bar for in browser web development tools. Until something can offer the same or better abilities as Firebug, I'm sticking with Firefox and Firebug for my web dev.
Re:Google Code Blog: Chrome Extensions for Web Development by rictic on Tuesday June 01, 2010 @02:09PM (#1395688)
Have you checked out the Web Inspector, built into Chrome and Safari? In my experience so far the only place it falls behind Firebug is in CSS editing, in every other way it seems superior. I'd be interested if you disagree.

More info: http://webkit.org/blog/829/web-inspector-updates/

Re:Google Code Blog: Chrome Extensions for Web Development by mrinterweb on Tuesday June 01, 2010 @04:54PM (#1396123)
I'll have to check out the built in developer tools more. live CSS editing is one of the main things I use Firebug for , for me, that is a big feature to be missing.

I do love the "Event Listeners" feature in the Developer Tools. That is very handy for easily finding what javascript events are unobtrusively bound to an element. So I can definitely see myself using the webkit developer tools in the near future.

Re:Google Code Blog: Chrome Extensions for Web Development by adamdecaf on Tuesday June 01, 2010 @11:35PM (#1396970)
It's a hack, but you can just edit the element inline (by double or right clicking the element under the "Elements" tag) and edit the styles via style="".
Re:Google Code Blog: Chrome Extensions for Web Development by loislo on Wednesday June 02, 2010 @02:54PM (#1398963)
You can add/edit/delete/css properties in the styles pane with help of double-click. It is not true live-edit but its working.
Re:Google Code Blog: Chrome Extensions for Web Development by pilif on Tuesday June 01, 2010 @08:09AM (#1394863)
What constantly seems missing is a way to change the user agent header. There is User-Agent Switcher for Chrome, but it only changes the Agent for JavaScript on the page - the header sent to the server is still the original one.

Presumably this is a limitation of the API provided to the extensions.

Re:Google Code Blog: Chrome Extensions for Web Development by adamdecaf on Tuesday June 01, 2010 @11:32PM (#1396959)
Run chrome from the command line

google-chrome --user-agent="Ipad"

Re:Google Code Blog: Chrome Extensions for Web Development by eekfuh on Tuesday June 01, 2010 @10:36AM (#1395128)
I'd like to start using Chrome for everything (currently I use Chrome for browsing, FF for dev) but until I can clear the cache with a single button AND be able to quickly delete the cookies for the domain I'm on at the time, I gotta keep using FF with webdev toolbar.
Re:Google Code Blog: Chrome Extensions for Web Development by jonursenbach on Tuesday June 01, 2010 @12:41PM (#1395459)
I really wish I were able to use SpeedTracer on Chrome and without having to append "--enable-extension-timeline-api" to the command line flag.
Re:Google Code Blog: Chrome Extensions for Web Development by ez77 on Tuesday June 01, 2010 @06:29AM (#1394753)
Re:Google Code Blog: Chrome Extensions for Web Development by ez77 on Tuesday June 01, 2010 @04:26PM (#1396047)
Could someone explain why Speed Tracer shows some "Script Evaluation" even for plain vanilla HTML pages with no <script> tags? I see two scripts: the first one has the URL field blank, while the second one reads "chrome-extension://ognampngfcbddbfemdapefohjiobgbdl/data_loader.js".

Thanks!

Re:Google Code Blog: Chrome Extensions for Web Development by ez77 on Tuesday June 01, 2010 @06:27AM (#1394752)
It's interesting that Google hasn't incorporated some of these extensions into their devtools.
Re:Google Code Blog: Chrome Extensions for Web Development by kellegous on Tuesday June 01, 2010 @07:21AM (#1394798)
Looks like that's going to happen soon. Speed Tracer is likely to become a part of Chrome's inspector, for instance.