Put the knife down and take a green herb, dude. (c) Ruffin Bailey 2001-2021

Step 1: Inspect the inspector. This horrendously tomato page talks about its importance, but only gives a top-level domain to figure out how to do it.

More success here -- Theming Chrome Dev Tools | Pixafy:

Once the Dev Tools are undocked, press Control Shift I (on Mac press Alt Command I), that new window that just popped up is the inspector for the first Dev Tools window!

Update 20140226: Apparently the Custom.css stuff is all gone. I've started using Chrome dev tools over Firebug more often, in large part b/c the RAM footprint of Chrome is lots smaller (today it was a 4x difference), but when I have my browser window in portrait, the Chrome dev tools layout stinks. Wanted to make the Sources source pane text smaller so that I could see more. I can, if I do the Control-Shift-I trick, above, and hack the "embedded" CSS, but that's not a persistent change.

Looks like there's no wonderful, supported way to do that, so I'll keep Ctrl-minus-ing for now.

Labels: chrome, firebug

Firefox world loses Web dev guru to Chrome | Deep Tech - CNET News:

Dion Almaer, who had worked on developer tools at Mozilla earlier in his career, noted the significance of [the lead Firebug programmer in 2011, John J.] Barton's new job in a blog post today.

"Firebug used to be the way you debugged your sites, but that is changed," Almaer said. "It is too early to claim that Firebug is zombied, but all eyes will be on that...especially as we see other browser tools continue to blossom."

I'm often a "if it's not broken, don't fix it" kind of guy (not a huge limitation, since my threshold for entering "broken" state is horribly low), and have been using Firebug as my first-line tester for years. I mean, heck, my code has to work in Firefox, so at worst, I'm only losing time that Firebug is worse than Chrome's tools (and that Firefox is slower than Chrome). That is, code has to work somewhere first. Why not Firefox?

But recently, I've heard too many good things from Chrome-first guys about Chrome's tools, have noticed that our app works insanely quicker in Chrome than Firefox, and am getting a little tired of seeing the "Warning: Enabling the Script panel causes a Firefox slow-down due to a platform bug. This will be fixed with the next major Firefox and Firebug versions," error at the top of my Firebug console. I usually use Chrome when hitting our production testing server, and thought maybe it was time to test it as my dev choice instead.

(And, honestly, I had some trouble with Chrome keeping its cache clean/empty when I last tried -- even when set to no cache, it would occasionally cache jive, which made it much too easy to waste time testing there.)

When Googling how to transition from Firebug to Chrome's tools, I ran across the above post. That's kinda strange -- I haven't felt Firebug was horrible, though I think I've seen a native Firefox equivalent pop up sometimes when I hit the "right wrong" key combination.

Anyhow, this is just to say I need to catch up with the state of browser debugging. Firebug is great, but it's probably past time to come up for air and see if the transition cost to something else isn't worth it.

Labels: chrome, firebug, firefox

title: Put the knife down and take a green herb, dude.	descrip: One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!! Back-up your data and, when you bike, always wear white. As an Amazon Associate, I earn from qualifying purchases. Affiliate links in green.
x MarkUpDown is the best Markdown editor for professionals on Windows 10. It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support. Features you won't find anywhere else include... MarkUpDown Multiline Table & Bootstrap Grid support. Beautiful Easy Actions that keep the Markdown flowing. HTML paste to paste HTML source into your documents. You've wasted more than $15 of your time looking for a great Markdown editor. Stop looking. MarkUpDown is the app you're looking for. Learn more or head over to the 'Store now!

Thursday, January 16, 2014
Experimenting with Chrome DevTools Themes Step 1: Inspect the inspector. This horrendously tomato page talks about its importance, but only gives a top-level domain to figure out how to do it. More success here -- Theming Chrome Dev Tools \| Pixafy: Once the Dev Tools are undocked, press Control Shift I (on Mac press Alt Command I), that new window that just popped up is the inspector for the first Dev Tools window! Update 20140226: Apparently the Custom.css stuff is all gone. I've started using Chrome dev tools over Firebug more often, in large part b/c the RAM footprint of Chrome is lots smaller (today it was a 4x difference), but when I have my browser window in portrait, the Chrome dev tools layout stinks. Wanted to make the Sources source pane text smaller so that I could see more. I can, if I do the Control-Shift-I trick, above, and hack the "embedded" CSS, but that's not a persistent change. Looks like there's no wonderful, supported way to do that, so I'll keep Ctrl-minus-ing for now. Labels: chrome, firebug posted by ruffin at 1/16/2014 12:37:00 PM

Monday, January 13, 2014
Firebug was all but zombied two years ago? Who knew? Firefox world loses Web dev guru to Chrome \| Deep Tech - CNET News: Dion Almaer, who had worked on developer tools at Mozilla earlier in his career, noted the significance of [the lead Firebug programmer in 2011, John J.] Barton's new job in a blog post today. "Firebug used to be the way you debugged your sites, but that is changed," Almaer said. "It is too early to claim that Firebug is zombied, but all eyes will be on that...especially as we see other browser tools continue to blossom." I'm often a "if it's not broken, don't fix it" kind of guy (not a huge limitation, since my threshold for entering "broken" state is horribly low), and have been using Firebug as my first-line tester for years. I mean, heck, my code has to work in Firefox, so at worst, I'm only losing time that Firebug is worse than Chrome's tools (and that Firefox is slower than Chrome). That is, code has to work somewhere first. Why not Firefox? But recently, I've heard too many good things from Chrome-first guys about Chrome's tools, have noticed that our app works insanely quicker in Chrome than Firefox, and am getting a little tired of seeing the "Warning: Enabling the Script panel causes a Firefox slow-down due to a platform bug. This will be fixed with the next major Firefox and Firebug versions," error at the top of my Firebug console. I usually use Chrome when hitting our production testing server, and thought maybe it was time to test it as my dev choice instead. (And, honestly, I had some trouble with Chrome keeping its cache clean/empty when I last tried -- even when set to no cache, it would occasionally cache jive, which made it much too easy to waste time testing there.) When Googling how to transition from Firebug to Chrome's tools, I ran across the above post. That's kinda strange -- I haven't felt Firebug was horrible, though I think I've seen a native Firefox equivalent pop up sometimes when I hit the "right wrong" key combination. Anyhow, this is just to say I need to catch up with the state of browser debugging. Firebug is great, but it's probably past time to come up for air and see if the transition cost to something else isn't worth it. Labels: chrome, firebug, firefox posted by ruffin at 1/13/2014 10:58:00 AM

Friday, August 23, 2013
Firebug: Debug code and access the console -- at the same time!!1! Gosh, I'm an idiot. Would have been nice to notice that button ("Show Command Line Popup") on the Script tab, well, YEARS AGO. Labels: firebug, firefox posted by ruffin at 8/23/2013 09:35:00 AM

<< Older \| Newer >>