Firebug 2.0 !

Showing 1-43 of 43 messages
Firebug 2.0 ! Jan Honza Odvarko 6/10/14 8:16 AM
Re: Firebug 2.0 ! Markus Staab 6/11/14 12:32 AM
thanks to the team for the hard work! its amazing!

could you pleaes also add the release to the beta channel, so we "nightly-testers" are not stuck on an older version then the release channel is atm...?

Thanks again!
Markus

On Tuesday, June 10, 2014 5:16:08 PM UTC+2, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Vito Meuli 6/11/14 4:07 AM
I had Firebug 1 working this morning.
After Firefox updated itself to 30.0 Firebug stopped working...
OK, then I updated Firebug to 2.0, but still not working.

I cannot find all my scripts in the Script panel, it shows just a few ones (there are over 400 indeed), so I cannot debug them.
Is it just me? :-)

Thanks for the good work!
Vito


Il giorno martedì 10 giugno 2014 17:16:08 UTC+2, Jan Honza Odvarko ha scritto:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Jan Honza Odvarko 6/11/14 4:23 AM
Hi Markus,
Firebug 2.0 beta 8 is already uploaded on AMO an it's exactly the same as Firebug 2.0

Honza
Re: Firebug 2.0 ! Jan Honza Odvarko 6/11/14 4:24 AM

On Wednesday, June 11, 2014 1:07:29 PM UTC+2, Vito Meuli wrote:
I had Firebug 1 working this morning.
After Firefox updated itself to 30.0 Firebug stopped working...
OK, then I updated Firebug to 2.0, but still not working.

I cannot find all my scripts in the Script panel, it shows just a few ones (there are over 400 indeed), so I cannot debug them.
Any chance we could load your page on our machines to check out the problem?

Honza
Re: Firebug 2.0 ! Jeff Shields 6/11/14 8:01 AM
Firebug 2.0 was automatically update this morning on my Window 7 64 bit machine with Firefox 30.0. Firebug fails to initialize Error on Line 39.

I have reverted to 1.12 for the time being. Not sure what I can do to help solve it, but let me know.

Jeff

On Tuesday, June 10, 2014 8:16:08 AM UTC-7, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Andy Leighton 6/11/14 9:31 AM
Chalk me up as another one who is having problems.

Currently on Firefox 30.0 / Firebug 2.0 but cannot get any Firebug UI to display at all.
Re: Firebug 2.0 ! Brian Wilkins 6/11/14 10:19 AM
I just wanted to add that I have the same issue as Jeff. Windows 7, 64 bit, Firefox 30.0. I don't receive an error message. The Firebug remains disabled even when I click the Firebug button on the toolbar. Yesterday I had version 1.12 and it worked fine.

Brian
Re: Firebug 2.0 ! Michael Patterson 6/11/14 1:24 PM

Hi, pretty cool.

Could be possible add a option in the html inpector -> css inpector in the next version? like in the image.

I love firebug, but, I usually I have problems when I starting with css, when I inspect an element, for example a div, if the div have some properties in a css file, is great because I can add more properties, but, when the element don't have any property in a css file, if I want to add some one to test, I need to click right -> add new attribute ->  style -> property, so, is not cool and take time, Chrome and firefox inspectors have this feature, is not a big deal, but it is very helpful.

Regards




On Tuesday, June 10, 2014 10:16:08 AM UTC-5, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Tom van der Laan 6/11/14 2:20 PM
Since the update to 2.0 the html side panel is gone and i have no idea how to get it back. Any idea on this?
Re: Firebug 2.0 ! Jan Honza Odvarko 6/11/14 11:28 PM
On Wednesday, June 11, 2014 7:19:41 PM UTC+2, Brian Wilkins wrote:
I just wanted to add that I have the same issue as Jeff. Windows 7, 64 bit, Firefox 30.0. I don't receive an error message. The Firebug remains disabled even when I click the Firebug button on the toolbar. Yesterday I had version 1.12 and it worked fine.
Brian, we need detailed instructions how to reproduce the problem.
As soon as we can see it, we can fix it.

Thanks
Honza
Re: Firebug 2.0 ! Jan Honza Odvarko 6/11/14 11:28 PM


On Wednesday, June 11, 2014 10:24:51 PM UTC+2, Michael Patterson wrote:

Hi, pretty cool.

Could be possible add a option in the html inpector -> css inpector in the next version? like in the image.

Please create a new enhancement request in our official issue list here:
https://code.google.com/p/fbug/issues/list

Honza
 

I love firebug, but, I usually I have problems when I starting with css, when I inspect an element, for example a div, if the div have some properties in a css file, is great because I can add more properties, but, when the element don't have any property in a css file, if I want to add some one to test, I need to click right -> add new attribute ->  style -> property, so, is not cool and take time, Chrome and firefox inspectors have this feature, is not a big deal, but it is very helpful.

Regards



On Tuesday, June 10, 2014 10:16:08 AM UTC-5, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: [firebug] Re: Firebug 2.0 ! Mike Baker 6/12/14 12:48 AM
I was having the same issue on OS X 10.9.3 with Firefox 30.0 after the upgrade to Firebug 2.0 from 1.12.8.  Clicking the Firebug Button produced no results (no error messages, no launch). 

Checking the /var/log/system.log for firefox references yielded a ton of these two messages (obviously with varying memory locations listed in each occurrence) after simply launching Firefox and doing nothing more:

6/12/14 1:07:39.000 AM kernel[0]: Data/Stack execution not permitted: firefox[pid 9790] at virtual address 0x1063df000, protections were read-write
6/12/14 1:17:32.000 AM kernel[0]: process firefox[9790] caught causing excessive wakeups. Observed wakeups rate (per sec): 151; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 74214
6/12/14 1:17:34.470 AM spindump[9899]: Saved wakeups_resource.spin report for firefox version 30.0 (3014.6.5) to /Library/Logs/DiagnosticReports/firefox_2014-06-12-011734_pmpmbp.wakeups_resource.spin
6/12/14 1:31:22.000 AM kernel[0]: firefox (map: 0xffffff803d5415a0) triggered DYLD shared region unnest for map: 0xffffff803d5415a0, region 0x7fff8ae00000->0x7fff8b000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
6/12/14 1:40:41.792 AM firefox[10038]: -deltaZ is deprecated for NSEventTypeMagnify.  Please use -magnification.

These repeat a number of times.  I remembered having a similar problem after I upgraded to 1.12.8, and thankfully was able to remember what I did to fix it way back then as well.  In that instance, I had an old plugin that was no longer being maintained and had remained in my Internet Plugin's folder from the previous version of Firefox after upgrade completion.  After removing the old plugin and restarting Firefox, I was able to launch Firebug without issue at that time.

Fast-forward to tonight with FB 2.0, and the same problem again.  I have no idea which of the following three plugins was at fault this time, but after doing the following maintenance to remove plugin's I hadn't used in a long time and restarting Firefox, I was able to finally launch FB2.0 and everything works as expected.  Note that simply "Disabling" the same 3 plugins listed below via Firefox's plugin management page didn't have any impact, I had to remove them from the Plugin directory.

  497  rm -rf XATTConnectEventEntry.plugin/
  498  rm -rf XStamps.com.plugin/
  499  rm -rf XExif\ Everywhere.plugin/

So it may be worth it for you guys hitting this problem to try removing yours one by one until you hopefully hit whichever is causing the trouble for you..  This might not actually be your problem given you're on Window's though, so I provide no guarantee of success using this method.  :-)

As a side note, on the Mozilla troubleshooting site (https://support.mozilla.org/en-US/kb/troubleshoot-issues-with-plugins-fix-problems?esab=a&s=manually+disable+plugin&r=6&as=s), the method for "Manually uninstalling a plugin" by placing an X in front of the name doesn't work. 

I'm not sure if its a 30.0 issue or Mac, or something else entirely, but in order to uninstall them you have to actually move the plugins out of the Plugin directory.  Adding the X leaves them enabled but with a new name with an X in front!  :-)  I'll be reporting this to them directly if an issue doesn't already exist.

Hope this helps!

- Mike


On Wed, Jun 11, 2014 at 1:19 PM, Brian Wilkins <brianw...@gmail.com> wrote:
I just wanted to add that I have the same issue as Jeff. Windows 7, 64 bit, Firefox 30.0. I don't receive an error message. The Firebug remains disabled even when I click the Firebug button on the toolbar. Yesterday I had version 1.12 and it worked fine.

Brian

--
You received this message because you are subscribed to a topic in the Google Groups "Firebug" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebug/6OfNxAMZFeY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/a3e1fa96-7edd-4eca-b446-25f391dcffb5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Re: [firebug] Re: Firebug 2.0 ! Jan Honza Odvarko 6/12/14 1:25 AM
I am also attaching a message from Andy:

"In my case it was a conflict with another add-on (Illuminations For Developers) .  So I would suggest that Brian has a similar issue and could maybe try disabling all his other addons and seeing if that works."

---

The first aid in weird cases is always checking whether other installed extensions (Firefox Add-ons) don't cause conflicts.

Honza



Re: Firebug 2.0 ! cheekybuddha 6/12/14 2:34 AM
Michael, you have always been able to do this with Firebug - it's just a little bit hidden.

When you have selected an element with no class, right-click on some whitespace in the Style panel and choose 'Edit Element Style'

Element.Style {

}

will appear in the panel and you can add the style you need. The way you have done it is the long way round.

hth,

d


On Wednesday, June 11, 2014 9:24:51 PM UTC+1, Michael Patterson wrote:
Could be possible add a option in the html inpector -> css inpector in the next version? like in the image.

I love firebug, but, I usually I have problems when I starting with css, when I inspect an element, for example a div, if the div have some properties in a css file, is great because I can add more properties, but, when the element don't have any property in a css file, if I want to add some one to test, I need to click right -> add new attribute ->  style -> property, so, is not cool and take time, Chrome and firefox inspectors have this feature, is not a big deal, but it is very helpful.


Re: Firebug 2.0 ! chen kefei 6/12/14 2:41 AM
i had the same problem.  it was conflict with add-on "Illuminations for Developers".  i have deactived the "Illuminations for Developers",  then firebug works again. may be at first you can try to deactivate the all other add-on except for firebugs. good luck :)


Am Mittwoch, 11. Juni 2014 18:31:11 UTC+2 schrieb Andy Leighton:
Chalk me up as another one who is having problems.

Currently on Firefox 30.0 / Firebug 2.0 but cannot get any Firebug UI to display at all.
Re: [firebug] Re: Firebug 2.0 ! Mike Baker 6/12/14 5:35 AM
Ah yes, given the hour when replying last night, I missed the fact I had also disabled the illumination for developers add-on along with removing the older plug-ins.  So it would seem the issue lies between those two!

- Mike
Re: Firebug 2.0 ! Michael Patterson 6/12/14 5:40 AM
Hi, thank you, very helpful,
yes, it is a little hidden

Regards
Re: Firebug 2.0 ! Ralph Dell 6/12/14 7:34 AM
On firebug 2.0 under my DOM panel my capitalized global variables were not showing. I rolled back to firebug  1.12.8bi and was able to see my capitalized globals. My browser is firefox 30.0. Can anyone confirm or deny that there is a prob

On Tuesday, June 10, 2014 11:16:08 AM UTC-4, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! r...@boll.ch 6/12/14 8:24 AM
Hello Jan

Since this automatic update to Firefox 30 I cannot debug anymore.
And I think I can tell you why.

I have one PHP file. This file generates all code HTML, Javascript, CSS dynamically in one file.
The generated code depends on some POST parameters (also the javascript code).

The old firebug recognized this somehow and told me, that I have reload the code. The original PHP
file with all parameters was loaded again to get the javscript code.

The new firebug just load my PHP file without any parameters. This causes an error and a crash in
my PHP file and only the code before this crash is loaded.

The javascript window looks like this then:

<script>
code..........  
</script>
<br><b>A database error has occurred</b><br>


The key point is: The file with the javascript code must be called
correctly (with parameters).

I hope my problem description is correct and this can be fixed.

Best Regards
Roland


Am Dienstag, 10. Juni 2014 17:16:08 UTC+2 schrieb Jan Honza Odvarko:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Jan Honza Odvarko 6/12/14 8:38 AM
Hi Roland,
can you please create a new issue report in our issue list here?
https://code.google.com/p/fbug/issues/list

And attach a test case (simple pages server/client you mentioned)
with baby step instructions how to use it, so we
can use it to reproduce the problem on our machines.
This would be great help.

Thanks!
Honza
Re: Firebug 2.0 ! Jan Honza Odvarko 6/12/14 8:46 AM


On Thursday, June 12, 2014 4:34:37 PM UTC+2, Ralph Dell wrote:
On firebug 2.0 under my DOM panel my capitalized global variables were not showing. I rolled back to firebug  1.12.8bi and was able to see my capitalized globals. My browser is firefox 30.0. Can anyone confirm or deny that there is a prob
Any chance I could load your page and test it on my machine?

Honza
 

On Tuesday, June 10, 2014 11:16:08 AM UTC-4, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Ralph Dell 6/13/14 7:48 AM
Here is a link

http://gis.catawbacountync.gov/template/inhouse2.html

I would expect to see MAP, CC and other globals.
Re: Firebug 2.0 ! Ralph Dell 6/13/14 8:01 AM
Here is a screen shot from 1.12.8bi
Re: Firebug 2.0 ! Jason Stonebraker 6/13/14 8:58 AM
Google maps failed to load with firebug open after the 2.0 update. Had to revert. Just a heads up.
Re: Firebug 2.0 ! Wilfredo Porta 6/13/14 10:43 AM
I've been using Firebug 2.0, and is very slow.

Try this:

Inspect an element (textarea for example) and try changing the width increasing it with the arrow keys from the css (HTML Panel - Styles). Changing the size is very slow.

Same behaviour with 1.12.8

Thanks.

El martes, 10 de junio de 2014 09:16:08 UTC-6, Jan Honza Odvarko escribió:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: Firebug 2.0 ! Jan Honza Odvarko 6/16/14 2:11 AM
On Friday, June 13, 2014 5:01:11 PM UTC+2, Ralph Dell wrote:
Here is a screen shot from 1.12.8bi


On Friday, June 13, 2014 10:48:02 AM UTC-4, Ralph Dell wrote:
Ralph, make sure to check "Show DOM Constants" option in the DOM panel
options menu (click the little black triangle next to DOM label to open the menu)

Does it help?

Honza
 

I would expect to see MAP, CC and other globals.

On Thursday, June 12, 2014 11:46:23 AM UTC-4, Jan Honza Odvarko wrote:


On Thursday, June 12, 2014 4:34:37 PM UTC+2, Ralph Dell wrote:
On firebug 2.0 under my DOM panel my capitalized global variables were not showing. I rolled back to firebug  1.12.8bi and was able to see my capitalized globals. My browser is firefox 30.0. Can anyone confirm or deny that there is a prob
Any chance I could load your page and test it on my machine?

Honza
 

On Tuesday, June 10, 2014 11:16:08 AM UTC-4, Jan Honza Odvarko wrote:
https://blog.getfirebug.com/2014/06/10/firebug-2-0/

Honza
Re: [firebug] Re: Firebug 2.0 ! Eduard Alexandru Stanciu 6/16/14 2:25 AM


On Thursday, 12 June 2014 11:25:15 UTC+3, Jan Honza Odvarko wrote:
I am also attaching a message from Andy:

"In my case it was a conflict with another add-on (Illuminations For Developers) .  So I would suggest that Brian has a similar issue and could maybe try disabling all his other addons and seeing if that works."

---

The first aid in weird cases is always checking whether other installed extensions (Firefox Add-ons) don't cause conflicts.

Honza


This was the same issue for me.
Thanks,
Eduard 
Re: Firebug 2.0 ! Ralph Dell 6/16/14 7:15 AM
After checking Dom Constants  the missing globals showed up at the bottom of the DOM list in normal case, not bold.  In the past my capitalized globals were at the top in bold.   Curiously enough I added another object with an uppercase name to my page and that showed up at the top of the DOM list in bold. If I can figure out if I am doing something to cause the different behavior I will post it.
I can now inspect my elements and that is what is important. I love firebug. Thank you for you help.
Re: Firebug 2.0 ! Simon Lindholm 6/18/14 4:39 PM
I'll take the blame for that problem with Dom Constants... :(

Fixed in https://code.google.com/p/fbug/issues/detail?id=7552.

- Simon
Re: Firebug 2.0 ! Sebastian Zartner 6/18/14 8:03 PM
@Wilfredo:
I can't reproduce this on Win8.1 with Firefox 30.0 + Firebug 2.0 on a machine with AMD C-70 processor.
What is "very slow" for you? Does it improve if you uncheck the HTML panel options Expand Changes and Highlight Changes?

Sebastian
Re: Firebug 2.0 ! Glenn 6/19/14 2:28 PM
@Sebastian: I have a similar problem on Iceweasel 30 & FB 2.0. Since the upgrade, the script panel is very laggy. Switching between scripts, for instance, was instantaneous before, and now takes about 1s to switch. Doesn't sound like much, but it's very annoying. Your suggestions don't improve it. 

My guess is that it's something to do with the syntax highlighting, but I don't see a way to turn it off to test. 
Re: Firebug 2.0 ! Sebastian Zartner 6/20/14 4:23 PM
@Glenn:
Wilfredo's problem was related to the HTML panel, not for the Script panel.
The reason why switching works slower than before may be due to the change to an asynchronous fetching of the script sources instead of synchronously fetching them. (@Honza: please correct me if I'm wrong.) The advantage of this asynchronous workflow is that the Script panel doesn't block the rest of the browser UI anymore. This step was necessary to adopt the new JSD2 debugging engine and get rid of the outdated and unmaintained JSD1 engine.
The speed of switching between scripts may be improved, though. Please create an issue for that, so this request is not lost in the noise.

Sebastian
Re: Firebug 2.0 ! Simon Lindholm 6/21/14 11:22 AM
Could be either that or the syntax highlighting. A lazy way of testing syntax highlighting performance is this:
1. Go to about:config, turn on devtools.chrome.enabled
2. Press Shift+F4 to open Scratchpad, and set it to Environment -> Browser
3. Open Firebug on some page
4. Run the following in Scratchpad:

e = Firebug.currentContext.getPanel("script").scriptView.editor
st = e.setText
e.setText = function(s, type) { st.call(e, Math.random() + "", type); }

and see how quick it is to switch between sources without actual script texts having to be syntax highlighted and displayed.
Re: Firebug 2.0 ! Glenn 6/22/14 5:52 PM
The random numbers show up instantly when I do this, so it sounds like the speed problem *is* related to syntax highlighting.  

Re: [firebug] Re: Firebug 2.0 ! San 6/23/14 12:14 PM
Sorry to be somewhat off-topic, but I keep reading in this thread about "capitalizing globals" (and even that Firebug's DOM display responds to that capitalization in some way). Is that standard or common formatting in JavaScript? I always thought capitalizing was just for constructors. Thanks.

Lawrence San
Business Writing: Santhology.com
Cartoon Stories for Thoughtful People: Sanstudio.com




--
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+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/6c3be20f-aa95-47c4-a034-abf729c00b34%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Re: [firebug] Re: Firebug 2.0 ! Simon Lindholm 6/24/14 10:03 AM
Capitalizing might have been the wrong word, what is referred to is ALL_UPPERCASE names. JavaScript has a few of those that are fairly useless, like document.ATTRIBUTE_NODE, so Firebug provides a way to hide them.
Re: Firebug 2.0 ! Peter Bonjernoor 7/6/14 8:41 AM
At the moment Firebug is not an option anymore for me. My main problems are with the debugger:
- it's impossibly slow. Every single action takes several seconds.
- flashing of other windows when stepping through the code
- breakpoints that are being ignored even when the code is clearly executed
- watches that insist of scrolling just out of view even though the content of the window didn't change

I've used Firebug with great pleasure for many years, but this is simply not workable anymore.
Re: Firebug 2.0 ! Sebastian Zartner 7/6/14 1:06 PM
On Sunday, July 6, 2014 5:41:24 PM UTC+2, peterbo...@gmail.com wrote:
At the moment Firebug is not an option anymore for me. My main problems are with the debugger:
- it's impossibly slow. Every single action takes several seconds.
Really? As far as I saw only switching between scripts takes a bit longer than before. Improving the performance of this is reported in issue 7560.
If other parts are slow, too, could you please try to run Firebug on a fresh profile and tell us if it's better?

- flashing of other windows when stepping through the code
Sound like issue 7512. Is it this what you see?
 
- breakpoints that are being ignored even when the code is clearly executed
Some breakpoint issues are fixed in Firebug 2.0.2 (which is currently on review on addons.mozilla.org). Please try it out and let us know if it fixes your issues. If not, it would be great if you reported the problem and attached a simple test case with steps to reproduce, so it can be fixed.
 
- watches that insist of scrolling just out of view even though the content of the window didn't change
I guess that's the same as reported in issue 4201, right?

Sebastian
Re: Firebug 2.0 ! Peter Bonjernoor 7/7/14 5:51 AM


Op zondag 6 juli 2014 22:06:54 UTC+2 schreef Sebastian Zartner:
On Sunday, July 6, 2014 5:41:24 PM UTC+2, peterbo...@gmail.com wrote:
At the moment Firebug is not an option anymore for me. My main problems are with the debugger:
- it's impossibly slow. Every single action takes several seconds.
Really? As far as I saw only switching between scripts takes a bit longer than before. Improving the performance of this is reported in issue 7560.
If other parts are slow, too, could you please try to run Firebug on a fresh profile and tell us if it's better?
Yes, really. A fresh profile with only Firebug 2.0.1 doesn't change a thing. It takes over 10 seconds to even appear after pressing F12, and even scrolling through the JS code is extremely sluggish.

- flashing of other windows when stepping through the code
Sound like issue 7512. Is it this what you see?
Yes, and the other window doesn't even have to be minimized
 
- breakpoints that are being ignored even when the code is clearly executed
Some breakpoint issues are fixed in Firebug 2.0.2 (which is currently on review on addons.mozilla.org). Please try it out and let us know if it fixes your issues. If not, it would be great if you reported the problem and attached a simple test case with steps to reproduce, so it can be fixed.
Hard to tell - it doesn't happen consistently
 
- watches that insist of scrolling just out of view even though the content of the window didn't change
I guess that's the same as reported in issue 4201, right?
More or less - it does seem to scroll down, but only just short of where it should be scrolling.

Sebastian
Oh, and try and set a breakpoint in a dragover handler - the cursor changes to nodrop, in all Firefox windows, and you can't click anything.

BTW - I'm not really looking for these issues to be resolved. With every new version both FF and FB are getting slower and slower in spite of running on a hex-core 16GB machine, and I just wanted to chime in and let you know that the current state of things is just not working for me. I'll be keeping an eye on how things develop over the coming months, and maybe come back to using FB again, because I do like it and I've gotten used to it. For now I'll be developing in Chrome though. :(
 
Re: Firebug 2.0 ! Sebastian Zartner 7/14/14 1:06 PM
On Monday, July 7, 2014 2:51:40 PM UTC+2, peterbo...@gmail.com wrote:
Op zondag 6 juli 2014 22:06:54 UTC+2 schreef Sebastian Zartner:
On Sunday, July 6, 2014 5:41:24 PM UTC+2, peterbo...@gmail.com wrote:
At the moment Firebug is not an option anymore for me. My main problems are with the debugger:
- it's impossibly slow. Every single action takes several seconds.
Really? As far as I saw only switching between scripts takes a bit longer than before. Improving the performance of this is reported in issue 7560.
If other parts are slow, too, could you please try to run Firebug on a fresh profile and tell us if it's better?
Yes, really. A fresh profile with only Firebug 2.0.1 doesn't change a thing. It takes over 10 seconds to even appear after pressing F12
Sorry, I can't reproduce that. For me it takes at maximum 3-5s until Firebug is shown. Anyway, this will be targeted with the next major version of Firebug.
 
and even scrolling through the JS code is extremely sluggish.
That will be part in the aforementioned issue.

Oh, and try and set a breakpoint in a dragover handler - the cursor changes to nodrop, in all Firefox windows, and you can't click anything.
This needs to be fixed by Firefox. See bug 1038092 and the related Firebug issue 5189.

Sebastian
Re: Firebug 2.0 ! Daryoush Ashtari 8/6/14 12:33 PM
I have Windows 8.1, 64-bit, Firefox 31. After Firebug updated to 2.0.2, it all the times returns error on the script in the head and repeat the first lien. practically, unusable and I had to disable it.

On Wednesday, June 11, 2014 8:31:11 PM UTC+4, Andy Leighton wrote:
Chalk me up as another one who is having problems.

Currently on Firefox 30.0 / Firebug 2.0 but cannot get any Firebug UI to display at all.
Re: Firebug 2.0 ! Sebastian Zartner 8/6/14 11:12 PM
Daryoush, I am not sure but I assume you're talking about issue 7615. Is that correct?

Sebastian
More topics »