From: Nicholas Clark Date: 11:40 on 01 Jun 2007 Subject: Firefox DOM Inspector When I have a line selected in the DOM inspector, and I *drag* the scrollbar, what do you think I want to do? a: Scroll? b: Initiate a drag-and-drop? And teasing me by giving me 'a' for half a second then swapping to 'b' isn't endearing you to me. Nicholas Clark
From: Nicholas Clark Date: 12:07 on 01 Jun 2007 Subject: Re: Firefox DOM Inspector On Fri, Jun 01, 2007 at 11:40:36AM +0100, Nicholas Clark wrote: > When I have a line selected in the DOM inspector, and I *drag* the scrollbar, Oh, sweet. If I re-load the page, you lose all the values. Software with alzheimer's. Just what I need. Nicholas Clark
From: Rafael Garcia-Suarez Date: 12:23 on 01 Jun 2007 Subject: Re: Firefox DOM Inspector On 01/06/07, Nicholas Clark <nick@xxxx.xxx> wrote: > When I have a line selected in the DOM inspector, and I *drag* the scrollbar, > what do you think I want to do? The DOM inspector is so hateful and useless that it would be a good thing to axe it off. Firebug is much nicer. (but that's off-topic)
From: Philip Newton Date: 12:29 on 01 Jun 2007 Subject: Re: Firefox DOM Inspector On 6/1/07, Rafael Garcia-Suarez <rgarciasuarez@xxxxx.xxx> wrote: > Firebug is much nicer. (but that's off-topic) I have a sneaking suspicion, that I'm too lazy to prove, that it's what's causing my Firefox to respond at a snail's pace. FF used to be my primary browser on this machine, with Opera being used for only certain things, for historical reasons, but I've been using Opera a whole lot more recently, despite the fact that it's an older version that doesn't do Ajax properly (among other things -- I tried installing a newer version once but it refused to speak to the proxy here). It's all hateful. Cheers,
From: A. Pagaltzis Date: 15:06 on 01 Jun 2007 Subject: Re: Firefox DOM Inspector * Philip Newton <philip.newton@xxxxx.xxx> [2007-06-01 13:35]: > On 6/1/07, Rafael Garcia-Suarez <rgarciasuarez@xxxxx.xxx> wrote: > >Firebug is much nicer. (but that's off-topic) > > I have a sneaking suspicion, that I'm too lazy to prove, that > it's what's causing my Firefox to respond at a snail's pace. Yes. Firebug drains a lot of CPU, even when "disabled". You have to bring up the extension manager and disable it for real to get your browser back. (You won't recognise Firefox -- *zippy*! Not an attribute you'd usually associate with that browser.) Of course, that requires a browser restart every time you want to toggle it on/off... but at least Firefox 2 can restart in place without losing your tabs... well at least not most of the time. Still, Firebug's CSS inspection facilities alone are worth it; problems that used to take me hours of guesswork to track down are suddenly matters of just 3 minutes of inspection and live meddling to verify my projected fix. The thing is painful and hateful in various ways, to be sure, but it's like going from sticks and stones to an assault rifle. Sure it might be a pain to clean out the suboptimally designed barrel sometimes... but it's such a leap in technology that whatever hatefulness it may embody just pales in the blinding brightness of progress it represents over the prehistoric tools of yesteryear. I would never go back to doing web stuff without it, despite the things I hate about it. Regards,
Generated at 10:26 on 16 Apr 2008 by mariachi