|Firebug 2.0.1||Jan Honza Odvarko||6/20/14 10:40 PM|
|Re: Firebug 2.0.1||Karol Čejka||6/24/14 5:30 AM|
i use firebug long time, and i love it.
But after this release i have big problem with firebug.
In tab scripts, it is combo with all active loaded JS files, but in this version i see only 50% of this files, and file what i need to see and debug, is not available.
In previous version it works well.
UpToDate Firefox 30.0 with Firebug 2.0.1
Thanks for your interest.
Dne sobota, 21. června 2014 7:40:28 UTC+2 Jan Honza Odvarko napsal(a):
|Re: Firebug 2.0.1||Jan Honza Odvarko||6/24/14 5:43 AM|
Do you have any other extensions installed?
Does it help if you install Firebug in a new fresh Firefox profile?
If none above helps, could I load your page on my machine to see the problem?
Is the page available online?
|Re: Firebug 2.0.1||hyun woo son lee||6/24/14 7:41 AM|
I was using firebug also for everything to develop in dojo, but with this new version in firefox 30 firebug 2.0.1, in scripts tab, only lists 4 js with the name of eval- dont load any js or library, i cant debug dojo
nor my application. In firefox 30 tried to install 1.12 firebug yet didnt work. So to make it work instaled firefox 29 with firebug 1.12.8 and worked !
Maybe its the firefox that prevents loading the js?
El sábado, 21 de junio de 2014 00:40:28 UTC-5, Jan Honza Odvarko escribió:
|Re: Firebug 2.0.1||Jan Honza Odvarko||6/24/14 8:28 AM|
Could you please provide a simple test case I could analyze a bit on my machine?
The best would be reporting a new issue in our issue list and attach the test to it.
|Re: Firebug 2.0.1||Juan Vaca||6/25/14 10:14 AM|
|Re: Firebug 2.0.1||fetis||6/25/14 2:51 PM|
The worst update ever. Breakpoints don't wok, debugger can freeze with no chance to reload or whatever.
On Saturday, June 21, 2014 9:40:28 AM UTC+4, Jan Honza Odvarko wrote:
|Re: Firebug 2.0.1||Carlos Santana||6/26/14 6:55 AM|
Can't confirm this.
After some initial problem, when it did not work at all, I am now back to normal working.
And I use FB several hours a day for JS and CSS work.
(WINDOWS 7/FF 30/FB 2.1)
|Re: [firebug] Re: Firebug 2.0.1||fetis||6/26/14 7:05 AM|
|Re: Firebug 2.0.1||Vito Meuli||6/30/14 8:58 AM|
Same problems for me:
* only a bunch of sources are visible in the debugger (they shoud be 411!!!)
* no way to debug a dojo application
The internal Firefox debugger has the same problems.
The problem arised when Firefox updated to 30 and I updated Firebug to 2.0.1.
Same problems starting from a fresh profile.
Maybe something in code validation changed in Firefox 30 or in Firebug 2.0.1?
I gues it's our dojo apps that have problems...
I'll go back to FF 29 (it's a pain...it keeps updating even when I stopped it from updating).
My two cents
Il giorno sabato 21 giugno 2014 07:40:28 UTC+2, Jan Honza Odvarko ha scritto:
|Re: Firebug 2.0.1||B Tuugii||7/2/14 12:34 AM|
No offence. But Firebug 2.0.1 is the biggest bullshit.
1. Breakpoints are like "release points". Breakpoints don't work what it supposed to do. It just let go.
2. Luckily if i get to debug the code step by step, it refreshes main page and some shit happens.
|Re: Firebug 2.0.1||Jan Honza Odvarko||7/2/14 1:10 AM|
Can you try test build attached here:
It contains a patch that should fix the problem.
Does it help?
|Re: Firebug 2.0.1||Siva Gopal||7/3/14 8:55 AM|
I am using Firebug from the last two years, but this version I don't have a clue about the behaviour of Firebug. I can simply say nothing is working in this version.
|Re: Firebug 2.0.1||Jan Honza Odvarko||7/3/14 9:07 AM|
On Thursday, July 3, 2014 5:55:09 PM UTC+2, Siva Gopal wrote:This is not helpful message. We need specific reports and a test cases we can use to see a problem. Then we can move ahead and fix it!
|Re: Firebug 2.0.1||DjBoo||7/9/14 11:31 PM|
Seems like Firebug 2.0/2.0.1 prevents Gmail Notifier extension to initiate. Any idea how to fix this?
Is there any open report related to addon SDK initiation?
|Re: Firebug 2.0.1||Jan Honza Odvarko||7/10/14 2:37 AM|
|Re: Firebug 2.0.1||John Banks||7/10/14 5:03 AM|
I'm going have to agree that the changes to Firebug really aren't an improvement.
1. Watch names are now being split down the middle with '...' For any kind of real time development this is not good. Even when you use copy name, you still don't get the real name of the watch.
2. While paused in script we used to be able to use the select HTML arrow and select an html item on the page. Not any more.
3. I have experienced multiple problems with ghost breakpoints. They are obviously being cached somehow even if they are deleted. I believe this may be reproducible by loading the browser with a vaild script
I have always said Firebug is the best JS development environment but these changes are truly effecting my ability to get work done. Hope we can some of these resolved quickly.
|Re: Firebug 2.0.1||Sebastian Zartner||7/10/14 5:59 AM|
thanks for the detailed feedback.
The reason behind this was to avoid horizontal scrolling as far as possible. OTOH DOM property names are not cropped, so this should probably be changed. Can you please create an issue for that with a small test case?
Obviously a bug. Please create an issue for that.
This is due to the new debugging API we use now. For more info follow issue 7348.
This was already reported several times. Unfortunately we can't reproduce this problem yet. So if you can provide a simple reproducible test case, then please post it in issue 7301.
|Re: Firebug 2.0.1||Marcello Pietrobon||7/10/14 8:33 AM|
|Re: Firebug 2.0.1||Jan Honza Odvarko||7/11/14 4:35 AM|
It's a platform (Firefox) bug, Firebug can't fix it.
(you might want to use Firebug 1.12.8 as a workaround)