I'm debugging a symphony app that sends out error messages as full fledged HTML pages with bells and whistles. Previously I could see the rendered version of the HTML in firefox by going to the Preview tab after selecting the request but a short while back they removed this feature. I am now forced to use Chrome for debugging. I can't see the point of Forgot dev edition of they have to remove useful dev features from it.
Saying Goodbye to Firebug
131–140 of 157 posts
Re: Saying Goodbye to Firebug
#132Does anyone know the history of the `console` object? The first time I ever saw it and used it was with Firebug, but it occurs to me that I don't know if Firebug invented it. Did it just decide to inject this name into the global namespace? And having it become a common API across multiple JS environments was due to its popularity in Firebug? Or was it somehow already in JS and I just wasn't aware of it up until that…
Netscape debugging http://www.codestore.net/store.nsf/unid/DOMM-4UZHEY
Re: Saying Goodbye to Firebug
#133Earlier quoted context omitted.
> I absolutely abhor the network panel in Chrome. What do you mean? There are plenty of ways to filter down the activity tab in Chrome if the problem you're experiencing is that the volume of requests is too high to be useful.
It is interesting that Network Panel in Firefox has built-in simple Postman-like tool [1] for editing request which you have already made. [1]: https://imgur.com/a/hBkmq // Chrome has copy as curl command.
Great for cheating at Facebook messenger games. Just send whatever score you like!
Re: Saying Goodbye to Firebug
#134Earlier quoted context omitted.
huh? How can one love firebug over Chrome Dev Tools? With the latter being just as revolutionary as firebug was when it first came out.
Revolutionary in what way? What could you do in Chrome Dev Tools when it first came out that you couldn't do in Firebug at the same time?
I think revolutionary as how Apple defines the word. They weren't the first but they sure had the panels running the smoothest.
Re: Saying Goodbye to Firebug
#135I know Firebug was great but it didn't usher in Web 2.0 > Jan 2007, Firebug 1.0 The start of Web 2.0! O'Reilly Media Web 2.0 Conference was in 2004 We than had the infamous Time Person of the Year "YOU" "TIME selected the masses of users who were participating in content creation on social networks, blogs, wikis, and media sharing sites."
That in itself doesn't mean much. At the time it was said that Web 2.0 is like teenage sex: everyone is talking about it, almost noone is doing it and those few that are doing it are doing it all wrong. :) I do agree that Firebug (as much as I miss it) didn't have much to do with Web 2.0 though.
I just hate how everyone has their own meanings for "Web 2.0". I wish the modern, JS-dependent web was versioned 3.0 or something.
Re: Saying Goodbye to Firebug
#136I'm on Firefox 56, but I believe Firebug worked in 55 still. The performance of Firebug fire exceeded the native browser tools. The inspector tool in Firebug was damn near instant to allow me to select an element in the browser. Firefox's version of the inspector can take upwards of 5 seconds sometimes to become "ready". Side note... I'm on a 7 year old macbook air, so the differences are very notable.
My experience as well lately dev tools are very sluggish in FF.
Re: Saying Goodbye to Firebug
#137Earlier quoted context omitted.
It is interesting that Network Panel in Firefox has built-in simple Postman-like tool [1] for editing request which you have already made. [1]: https://imgur.com/a/hBkmq // Chrome has copy as curl command.
You should log out and back in if you haven't already. That screenshot contains almost your entire session token.
Yeah, I know. I made that screenshot, signed out, uploaded this file, then logged in to post my previous comment. Thank you for reminding anyway :)
Re: Saying Goodbye to Firebug
#138Firebug was the greatest thing to happen to web development. Honestly I still prefer it to the native dev tools. I especially love how most things go to the console so I don't have to jump all over the place to find the information I'm looking for. I absolutely abhor the network panel in Chrome. It's like they're purposefully trying to make it difficult.
I noticed in recent firefox-dev you can now expand XHR requests directly in the console which then pops up a mini network panel. I don't know how long it's been there, I noticed it today but I might have simply had XHR logging off previously.
It's been here for a long time, but by default the console has several filters disabling some output, including XHR. So most people don't know about it.
Re: Saying Goodbye to Firebug
#139Earlier quoted context omitted.
Revolutionary in what way? What could you do in Chrome Dev Tools when it first came out that you couldn't do in Firebug at the same time?
I think revolutionary as how Apple defines the word. They weren't the first but they sure had the panels running the smoothest.
Boy, I missed the time when we used "revolutionary" for, you know, revolutionary things.
Re: Saying Goodbye to Firebug
#140Earlier quoted context omitted.
Revolutionary in what way? What could you do in Chrome Dev Tools when it first came out that you couldn't do in Firebug at the same time?
I think revolutionary as how Apple defines the word. They weren't the first but they sure had the panels running the smoothest.
That makes no sense, GP stated the chrome devtools were just as revolutionary as firebug was when it first came out. Not just "meaninglessly revolutionary" but more revolutionary than the one tool at the origin of all modern web devtools.