| 22:30 | <jgraham> | I hink this is the point at which I bitch about the current state of airports in northern europe |
| 22:30 | <jgraham> | +t |
| 22:33 | <oojacoboo> | are there any plans to improve the inspector tools in Chrome? |
| 22:34 | <AryehGregor> | oojacoboo, they're being improved on a regular basis. |
| 22:34 | <oojacoboo> | I'd love to make the switch from firefox to Chrome, but the current dev tools make my css work much more difficult, over firebug, and birebug lite is just not good enough for solid use |
| 22:34 | <AryehGregor> | Interesting. I found Web Inspector good enough for my purposes, but I suppose I don't do so much front-end development. |
| 22:34 | <AryehGregor> | If there are specific missing features you'd like, the Chrome/WebKit people would undoubtedly appreciate it if you filed bugs. |
| 22:35 | <webben> | oojacoboo: improve them to do what? |
| 22:35 | <AryehGregor> | I guess they know that's a reason a lot of people use Firefox instead, so they're eager to improve it. |
| 22:35 | <AryehGregor> | When I filed a bug asking for a new Web Inspector feature, it was added pretty quickly. |
| 22:35 | <AryehGregor> | (YMMV) |
| 22:35 | webben | never understood what firebug lite offered over webkit inspector |
| 22:35 | <oojacoboo> | the one thing that is keeping me back is inspection on element and color based element identification |
| 22:36 | <webben> | oojacoboo: do you mean highlighting the element in the page |
| 22:36 | <oojacoboo> | for instance, inspect an element, then hover over it in the html DOM and it will highlight that elements box model |
| 22:36 | <oojacoboo> | but everything is blue, you can't tell if it's padding, margin, or what |
| 22:36 | <oojacoboo> | in firebug, I can do this and know within a second exactly the issue |
| 22:36 | <AryehGregor> | Yeah, that's nice in Firebug. |
| 22:37 | <oojacoboo> | huge |
| 22:37 | <oojacoboo> | probably saves me hours a week |
| 22:37 | <webben> | oojacoboo: sounds worthy of an RFE |
| 22:37 | <oojacoboo> | RFE? |
| 22:38 | <webben> | request for enhancement |
| 22:38 | <oojacoboo> | also, the layout inspector is much nicer to look at on firebug |
| 22:39 | <oojacoboo> | and the tabs across the top to access that or the styling, is much quicker for navigation and scrolling down the collapsable list |
| 22:39 | <oojacoboo> | s/and/than |
| 22:40 | <oojacoboo> | I think that the Chrome team would find themselves seeing a lot more developers jumping onboard if they improved the dev tools |
| 22:40 | <oojacoboo> | and as we all know, when developers choose to go one way, others tend to follow |
| 22:41 | <oojacoboo> | I've been holding out for about 2 years now on Chrome waiting for firebug or something decent |
| 22:42 | <AryehGregor> | oojacoboo, you should really try filing bugs asking for specific missing features. |
| 22:42 | <AryehGregor> | They're browser implementers, they're not going to know what web developers want exactly. |
| 22:42 | <oojacoboo> | I would if it didn't require so much work |
| 22:43 | <AryehGregor> | It doesn't require work. |
| 22:43 | <oojacoboo> | a form with 30 elements == work |
| 22:43 | <AryehGregor> | http://code.google.com/p/chromium/issues/entry |
| 22:43 | <AryehGregor> | I count three elements. |
| 22:43 | <oojacoboo> | mmm |
| 22:43 | <oojacoboo> | must have been mozillas that was so bad |
| 22:43 | <AryehGregor> | Mozilla's is okay these days too. |
| 22:44 | <oojacoboo> | bugzilla... that is a pile of shit |
| 22:44 | <oojacoboo> | worst ui on the planet |
| 22:44 | <AryehGregor> | Bugzilla has very bad UI, yes. |
| 22:45 | <AryehGregor> | Google Code's tracker has very nice UI, though. |
| 22:45 | <oojacoboo> | yea, this looks ok |
| 22:45 | <oojacoboo> | I can actually tell what's going on |
| 22:48 | <oojacoboo> | submitted |
| 22:48 | <oojacoboo> | http://code.google.com/p/chromium/issues/detail?id=67512 |