Sorry for the extreme delay on this! On Thursday, December 8, 2016 at 1:03:47 PM UTC+1, pd wrote: > > How many of these items have been implemented Sebastian? >
These are the suggestions for what should get implemented. They are not implemented yet. Though what I've heard, they will be worked on in the first quarter of 2017. On Thursday, December 8, 2016 at 6:36:25 PM UTC+1, sm...@virtuluxe.com wrote: > > I cannot use this new tool at all. Where is the side by side console that > allowed multiple line script and loading of scripts from history? I have > been using this tool since it's inception and now we are forced to use a > different browser. > Instead of the Command Editor <https://getfirebug.com/wiki/index.php/Command_Editor>, there is a tool called Scratchpad <https://developer.mozilla.org/en-US/docs/Tools/Scratchpad>, which works more or less the same. Also, you can add a line break while typing into the command line by pressing Shift+Enter. Furthermore, there's a request for adding a multi-line editor to the command line <https://bugzilla.mozilla.org/show_bug.cgi?id=1133849>. On Thursday, December 8, 2016 at 6:36:25 PM UTC+1, David Smith wrote: > > The Firefox dev tools has ruined my development. Now I need to find a new > browser to develop one. Sad day. > This is the chance to explain why exactly they're not sufficient for you. On Friday, December 9, 2016 at 12:20:12 AM UTC+1, David Smith wrote: > > I do not know what prompted this move > See the point "What about Firebug 2" in the latest related blog post <https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/> and also former blog posts about this. It's not so much that they can do the same sort of things but differently, > it's also a rote memory issue > For this reason I've created a migration guide <https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug>. It's not complete yet, though, so anyone willing to help, please do so! > Now I find myself trying to figure out what this prompt means "The Web > Console logging API (console.log, console.info, console.warn, > console.error) has been disabled by a script on this page" when I open the > console. > That means that you probably had Firebug open before the DevTools. Firebug injects the console object into the page and the DevTools don't overwrite it with their console object when it's already defined. So, just deactivate Firebug and reload the page. On Friday, December 9, 2016 at 4:25:01 AM UTC+1, San wrote: > > David Smith <sm...@virtuluxe.com> wrote: > >> Yes, I can stay at the version and continue to run Firebug (I am quite >> certain that I cannot have two versions on the same Mac) > > > Luckily -- despite your being "quite certain" -- that's not true, or at > least it didn't used to be true. I have a free program called MultiFirefox > <http://davemartorana.com/multifirefox/> installed on my Mac... > I don't know how you do it on Mac, though on Windows it is very easy. You just choose another installation directory when installing it and that's it. Anyway, staying at an old Firefox version is not a longterm solution, because you'll miss the platform features the new versions introduce. On Friday, December 9, 2016 at 9:09:08 PM UTC+1, Erik Krause wrote: > > Am 09.12.2016 um 00:19 schrieb David Smith: > > I do not know what prompted this move, > > whether it is internal politics, a financial or corporate decision, but > it > > is a monumental change for the people that develop with Firebug. > > Firebug was an extension to Firefox, built by volunteers. There where > not enough of them to switch to multi process architecture. The devtools > are built-in, they come from mozilla. ... > > The devtools are more or less usable now and in some aspects even better > than firebug. ... > > So you, who are working in the fastest changing industry in the world, > be a bit more flexible and give a new tool a chance. And go to bugzilla > and vote for the bugs that annoy you most. > My words. Thank you, Erik! Yes, the DevTools are currently missing some of Firebug's features and are slower, though they already have many more features than Firebug and also have some features even the Chrome DevTools don't offer yet like the upcoming CSS Grid Inspector. <https://hacks.mozilla.org/2016/12/css-grid-and-grid-highlighter-now-in-firefox-developer-edition/> On Saturday, December 10, 2016 at 11:11:36 PM UTC+1, alfonsoml wrote: > I try to keep an open mind and use all the browsers a little, rotate the > usage, understand what are the improvements that each dev tools have, but > so far I still haven't found anything that makes the native DevTools of > Firefox anything special. > The Animations side panel <https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Work_with_animations> is an example. Erik mentioned some more. > It includes options that I will never use, but it lacks features that were > present in Firebug. So currently Firefox is my last option when I want to > debug something complex. > If you have specific features in mind which were not mentioned yet, please share them. On Sunday, December 11, 2016 at 12:22:31 PM UTC+1, Denis Chenu wrote: > > Maybe the best is to put bug report on the best place : > https://bugzilla.mozilla.org . See > https://bugzilla.mozilla.org/show_bug.cgi?id=991806 for example ? > Correct. If you miss anything not blocking bug 991806 yet, please file a new bug in Bugzilla and mark it as blocker of 991806. On Friday, December 16, 2016 at 4:17:41 PM UTC+1, Arvis Pinkletter wrote: > > The Debugger tab - in "sources", when I am working on a site where you > have to log in to see the page, I need the "source" of the page I'm working > on to be the same as the one in the browser, that is, if I'm logged into > the site, the source in the debugger tab for that page should also be the > "logged in" version of the page. Our pages redirect you to a login page if > you aren't logged in, so currently, in my "source" tab if I'm trying to > work on something, I see the markup and scripting for the login page > instead of the page I actually want. What's weird about this is that the > "inspector" tab has the right content, but not the debugger tab. > Do you have a URL, so this can be reproduced? Did Firebug (before Firefox 50) show different results? Also, scrolling up and down in the debugger tab isn't as nice as in the > inspector tab; I can't use my mouse pointer on the scroll bar - I have to > use my wheel or my keyboard to page up and down. > The Debugger panel is currently reworked <https://github.com/devtools-html/debugger.html> for a better UI and to be independent of the DevTools. You may try it out in the latest Developer Editions <https://aurora.mozilla.org/> and Nightlies <https://nightly.mozilla.org/> of Firefox. Try it out and let them know if it's still not working for you. On Friday, December 16, 2016 at 9:25:30 PM UTC+1, Arvis Pinkletter wrote: > > Console Tab: >> > XHR requests have "Headers", "POST", "Response", "Call Stack". > Need these that Firebug had: "JSON" (the nicely navigable JSON object that > is the Response), and "Cookies" > The JSON structure is available inside the *Response* tab. I'll add that to the migration guide <https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug>. Sebastian -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/49e64422-662c-4502-b5f5-8e74bce753d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
