Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Saurabh Anand
    @sawrubh
    Is NetExport supported yet in Firebug 3 alpha?
    Jan Odvarko
    @janodvarko
    Basic HAR export landed in Firebug 3 alpha 6, see more in issue #243
    Alistair Laing
    @aliuk2012
    Who maintains Firebug.next wiki? Theres a bit of contradiction on how to setup and develop for firebug.next. The GitHub Repo suggests using JPM but the Wiki says you need to use cfx. Obviously JPM is the new standard way.
    Jan Odvarko
    @janodvarko
    Yes, JPM is the new and recommended way. Where exactly is the note about CFX? I'll fix it.
    It's in the development tools and tricks section
    Alistair Laing
    @aliuk2012
    @anurag90x thats it
    @janodvarko do you need help with renaming the files?
    Jan Odvarko
    @janodvarko
    Thanks the wiki is fixed
    @anurag90x yep, that would be great!
    Alistair Laing
    @aliuk2012
    I know people recommend using jshint should we not include it as part of the npm install? Any thoughts about using grunt.js to watch for file changes and then to compile xpi or to run jpm tests?
    Saurabh Anand
    @sawrubh
    Can we have a system for updating Firebug.next (say from 3.0.0-alpha.6 to alpha.7) automatically (by checking for updates for extensions in about:addons) instead of having to download the xpi manually and the least we could do is allow downloading the xpi from GitHub itself or someplace easier to access instead of finding https://getfirebug.com/releases/firebug/3.0/.
    Florent Fayolle
    @fflorent
    Right. We're updating the README.md file.
    Note that if you download Firebug.next from https://getfirebug.com/releases/firebug/3.0/, you should be able to update Firebug.next automatically. Doesn't doing so work for you?
    Florent Fayolle
    @fflorent
    @sawrubh ^
    Saurabh Anand
    @sawrubh
    @fflorent It didn't automatically update for me from 6 to 7. I'll give it a try next time (from 7 to 8) and let you know if it works.
    Florent Fayolle
    @fflorent
    @sawrubh thanks :-)
    Joeri Boudewijns
    @bojoer
    I've just been testing on the Firefox Dev with the new Firebug which is build on top off the native Firefox Dev Tools, Console etc....
    Must say that, so far as I have been able to test it, it works great except addinional Firebug addons don't seem to work although they installed fine. e.g.: FirePHP, Illuminations, Omnibug etc... but that should be fixed on final stable release, I hope :smile: little :worried: but also a :+1:
    Jan Odvarko
    @janodvarko
    Yes, we are planning to port some of those extensions or help the authors to port it.
    Jan Odvarko
    @janodvarko
    @sawrubh the auto-update should be fixed now, please let me know if it works for you, thanks.
    Jan Odvarko
    @janodvarko
    Jan Odvarko
    @janodvarko
    Christoph Dorn
    @cadorn
    What is the ETA for the Firebug.next BETA now? I am actively working on updating FirePHP and hope to have something working along with the release.
    Jan Odvarko
    @janodvarko
    Next week I guess...
    Christoph Dorn
    @cadorn
    @janodvarko Any pointers? firebug/devtools-extension-examples#1
    self.port... does not work
    Iulian Onofrei
    @revolter
    Is there a setting to disable auto js beautifier? Or it does that automatically for me because of other plugin? I forgot what was the default. The problem is that on some sites with big minified js file, if I have Firebug opened, it freezes for some time and then it sends the Continue|Stop script alert
    Daniel Dimitrov
    @compojoom
    wow, so this is where the cool kids are hanging out those days :D
    Jan Odvarko
    @janodvarko
    Yeah, we are all here ;-)
    Iulian Onofrei
    @revolter
    @janodvarko, could you help me please with the previous question?
    Jan Odvarko
    @janodvarko
    @revolter the js prettifier is implemented natively in Firefox, but you can switch it off by the "{}" icon in the Debugger panel (at the bottom of the left side panel, the source list)
    Daniel Dimitrov
    @compojoom
    do you guys by any chance have an idea how to debug a FF hang? https://crash-stats.mozilla.com/report/index/6e2dac84-90e1-4a8f-8a31-26df12150331 I always get FF to hang on some pages & I would like to find out how to debug this
    but I have no clue where to start...
    Iulian Onofrei
    @revolter
    @janodvarko, Thanks! @compojoom, This is exactly my problem too. If it is of any help, an website where it does this is built using Ember, so lots of javascript
    Daniel Dimitrov
    @compojoom
    @revolter are you talking as well for the view source? This is not a FB bug, but something with FF...
    Iulian Onofrei
    @revolter
    @compojoom Sorry, I misread your comment. It hangs me with the FB opened, not view source.
    Daniel Dimitrov
    @compojoom
    I've had similar problems with FB in the past, but this time it's not FB :)
    Florent Fayolle
    @fflorent
    @compojoom Sorry for the late reply. Do you have a always reproducible scenario for this (by chance)?
    Daniel Dimitrov
    @compojoom
    @fflorent - yes, I do. Happens always on my localhost when joomla's debug is on.
    Joseph Castro
    @JosephCastro
    Hi, I want to help with this: firebug/firebug.next#384 , Anyone can give a clue from where to start ?
    Jan Odvarko
    @janodvarko
    @JosephCastro I can help you, I just commented within the bug report
    Mark Lagendijk
    @marklagendijk
    @janodvarko when do you expect that Firebug 3 will get to beta?
    I can imagine that you don't know exactly, but maybe you could give a rough estimate
    Jan Odvarko
    @janodvarko
    I dont know precisely when the beta is going to start, but Firebug 3 should be ready when e10s is enabled by default for all Firefox users (i.e. when its enabled in the release channel)
    Jeroen van Warmerdam
    @jerone
    Is there an issue to subscribe for Firebug beta or FF e10s enabling?
    Jan Odvarko
    @janodvarko
    I think that e10s should be enabled in Firefox 42 (and than it needs some time to propagate through the distribution channels to the final release)
    Rico042002
    @rico042002
    Can someone please help me
    Im about to give up on mozilla and firebug if this continues
    Iulian Onofrei
    @revolter
    What?