I don't mean to piss on all the important work, but somehow I am on the "release update channel" and as of about 7PM on July 13, my development has screeched to a halt as a result of many changes and seemingly broken features. What I find problematic is that I am not sure how this software upgraded itself on my system without so much as a prompt for permission. I am now on track to miss my deadline, thanks to this untimely update.
On my system, Firebug 1.10.0 is running with Firefox 13.0.1.
1. The first problem issue, noticed on July 13th was the delayed load feature. While inconvenient for development, I certainly understand that quick-start is an important production feature. So I have worked around this, although not without pain...
2. When I am able to drop down the "about Firebug" menu, it indicates "1.10.0" Sometimes the menus in Firebug are frozen in a state where they flash and are overlayed with the content of the page, making them non-navigable. When this occurs, all of the drop-downs are impacted. But the one that makes it impossible to use is when "Script" is selected and the script file dropdown reads "Inline" and the dropdown next to "Inline" simply flashes the names of the script files, but does not allow any to be selectable...
I need to get back to a working system.
Any suggestions for compatible Firebug/Firefox versions to backtrack to?
On Jul 16, 5:22 am, nonneophyte <kam...@digital-parts.com> wrote:
> I don't mean to piss on all the important work, but somehow I am on the
> "release update channel" and as of about 7PM on July 13, my development has
> screeched to a halt as a result of many changes and seemingly broken
> features. What I find problematic is that I am not sure how this software
> upgraded itself on my system without so much as a prompt for permission. I
> am now on track to miss my deadline, thanks to this untimely update.
> On my system, Firebug 1.10.0 is running with Firefox 13.0.1.
> 1. The first problem issue, noticed on July 13th was the delayed load
> feature. While inconvenient for development, I certainly understand that
> quick-start is an important production feature. So I have worked around
> this, although not without pain...
You can also try to set this pref to false:
extensions.firebug.delayLoad
> 2. When I am able to drop down the "about Firebug" menu, it indicates
> "1.10.0" Sometimes the menus in Firebug are frozen in a state where they
> flash and are overlayed with the content of the page, making them
> non-navigable. When this occurs, all of the drop-downs are impacted. But
> the one that makes it impossible to use is when "Script" is selected and
> the script file dropdown reads "Inline" and the dropdown next to "Inline"
> simply flashes the names of the script files, but does not allow any to be
> selectable...
Could you send detailed instructions how to repro the problem?
If you go back to Firebug 1.9.2, does it still happen?
Could it be Firefox bug?
> > 2. When I am able to drop down the "about Firebug" menu, it indicates > > "1.10.0" Sometimes the menus in Firebug are frozen in a state where they > > flash and are overlayed with the content of the page, making them > > non-navigable. When this occurs, all of the drop-downs are impacted. But > > the one that makes it impossible to use is when "Script" is selected and > > the script file dropdown reads "Inline" and the dropdown next to > "Inline" > > simply flashes the names of the script files, but does not allow any to > be > > selectable... > Could you send detailed instructions how to repro the problem? > If you go back to Firebug 1.9.2, does it still happen? > Could it be Firefox bug?
This can normally be fixed by turning off hardware acceleration via *Firefox Button > Options > Advanced > General > Use hardware acceleration when available*. And yes, this is a reported Firefox bug<https://bugzilla.mozilla.org/show_bug.cgi?id=679287> .
Thanks for the quick response. I am not sure what made the
"script-selection-not-possible" problem go away. But it is gone now,
without any adjustment of the "hardware acceleration" settings, which on my
system is still set to "use when available."
Also, the description of that
bug<https://bugzilla.mozilla.org/show_bug.cgi?id=679287>is that the
menu item appears transparantly. That was not what I was
seeing. The dropdown(s) would continually flash at high speed, but they
were completely unselectable, for as long as you would keep the tab
selected.
Once I was able to clear all breakpoints and exit and restart several
times, and progress my code, I have been able to make good progress using
the latest release, with no further incidents. My code has evolved
considerably now, so it could have been anything.
The problem wasn't just that the "*script*" file tab selector dropdown was
not selectable. When this occurred, also the "*Breakpoints*" tab had the
same problem. This made it almost impossible to do anything except exit and
start over. But for a while Firebug was stuck in that state or it recurred
several times. When I attempted to drop down the selector triangle it
flashed the choices, which were instantly overlayed by the content of the
source code display frame or the content of the Breakpoint list.
It was possible to drop down Console and DOM during this failure.
If it happens again, I'll make a better effort to isolate it. But first I
would need to take myself off the auto-update, otherwise isolating anything
is impossible...
On Mon, Jul 16, 2012 at 3:04 AM, Jan Honza Odvarko <odva...@gmail.com>wrote:
> On Jul 16, 5:22 am, nonneophyte <kam...@digital-parts.com> wrote:
> > I don't mean to piss on all the important work, but somehow I am on the
> > "release update channel" and as of about 7PM on July 13, my development
> has
> > screeched to a halt as a result of many changes and seemingly broken
> > features. What I find problematic is that I am not sure how this software
> > upgraded itself on my system without so much as a prompt for permission.
> I
> I guess you have auto-update on. Check this post about how to disable
> it
> > am now on track to miss my deadline, thanks to this untimely update.
> > On my system, Firebug 1.10.0 is running with Firefox 13.0.1.
> > 1. The first problem issue, noticed on July 13th was the delayed load
> > feature. While inconvenient for development, I certainly understand that
> > quick-start is an important production feature. So I have worked around
> > this, although not without pain...
> You can also try to set this pref to false:
> extensions.firebug.delayLoad
> > 2. When I am able to drop down the "about Firebug" menu, it indicates
> > "1.10.0" Sometimes the menus in Firebug are frozen in a state where they
> > flash and are overlayed with the content of the page, making them
> > non-navigable. When this occurs, all of the drop-downs are impacted. But
> > the one that makes it impossible to use is when "Script" is selected and
> > the script file dropdown reads "Inline" and the dropdown next to "Inline"
> > simply flashes the names of the script files, but does not allow any to
> be
> > selectable...
> Could you send detailed instructions how to repro the problem?
> If you go back to Firebug 1.9.2, does it still happen?
> Could it be Firefox bug?
> > > Firebug team is proud to release final Firebug 1.10!
> > > Honza
> --
> You received this message because you are subscribed to the Google
> Groups "Firebug" group.
> To post to this group, send email to firebug@googlegroups.com
> To unsubscribe from this group, send email to
> firebug+unsubscribe@googlegroups.com
> For more options, visit this group at
> https://groups.google.com/forum/#!forum/firebug
-- Ken Amron
Digital Parts, Inc.
877.374.4300 ext. 567
> Thanks for the quick response. I am not sure what made the > "script-selection-not-possible" problem go away. But it is gone now, > without any adjustment of the "hardware acceleration" settings, which on my > system is still set to "use when available."
Ok, good.
> Also, the description of that bug<https://bugzilla.mozilla.org/show_bug.cgi?id=679287>is that the menu item appears transparantly. That was not what I was > seeing. The dropdown(s) would continually flash at high speed, but they > were completely unselectable, for as long as you would keep the tab > selected.
I see.
> The problem wasn't just that the "*script*" file tab selector dropdown > was not selectable. When this occurred, also the "*Breakpoints*" tab had > the same problem. This made it almost impossible to do anything except exit > and start over. But for a while Firebug was stuck in that state or it > recurred several times. When I attempted to drop down the selector > triangle it flashed the choices, which were instantly overlayed by the > content of the source code display frame or the content of the Breakpoint > list.
> It was possible to drop down Console and DOM during this failure.
> If it happens again, I'll make a better effort to isolate it.
Yes, please. Without seeing the problem by ourselves we can't fix it. Anyway, thanks for the feedback on this.
Firebug 1.10 has conflict with NetVideoHunter, if both installed, the NetVideoHunter addon could not be used normally. But it works ok with Firebug 1.9.2.
This looks more of an issue in NetVideoHunter. So please contact them via i...@netvideohunter.com, refer to this thread and tell them they should write us if they need help.
On Tuesday, July 24, 2012 5:01:51 AM UTC+2, Yanfang Liu wrote:
> Hi Honza,
> I want to report a issue:
> Firebug 1.10 has conflict with NetVideoHunter, if both installed, the > NetVideoHunter addon could not be used normally. But it works ok with > Firebug 1.9.2.
Great product! However, how do I change the hot-keys in my 10.7.4 Mac running the latest FIREFOX. I want to change the hot key combination of a few controls. In dire need.
On Friday, July 27, 2012 2:35:29 PM UTC+5:30, Sebastian Zartner wrote:
> Honza is currently in vacations.
> This looks more of an issue in NetVideoHunter. So please contact them via > i...@netvideohunter.com, refer to this thread and tell them they should > write us if they need help.
> Sebastian
> On Tuesday, July 24, 2012 5:01:51 AM UTC+2, Yanfang Liu wrote:
>> Hi Honza,
>> I want to report a issue:
>> Firebug 1.10 has conflict with NetVideoHunter, if both installed, the >> NetVideoHunter addon could not be used normally. But it works ok with >> Firebug 1.9.2.
>> Pls help to check this issue. Thanks very much!
On Aug 2, 9:01 am, Shreyas Agasthya <shreya...@gmail.com> wrote:
> Guys,
> Great product! However, how do I change the hot-keys in my 10.7.4 Mac
> running the latest FIREFOX. I want to change the hot key combination of a
> few controls. In dire need.
> On Aug 2, 9:01 am, Shreyas Agasthya <shreya...@gmail.com> wrote:
> > Guys,
> > Great product! However, how do I change the hot-keys in my 10.7.4 Mac
> > running the latest FIREFOX. I want to change the hot key combination of a
> > few controls. In dire need.
> Firebug (icon) menu -> Customize Shortcuts
> opens a dialog to customize shortcuts.
> Does it help?
> Honza
> --
> You received this message because you are subscribed to the Google
> Groups "Firebug" group.
> To post to this group, send email to firebug@googlegroups.com
> To unsubscribe from this group, send email to
> firebug+unsubscribe@googlegroups.com
> For more options, visit this group at
> https://groups.google.com/forum/#!forum/firebug
> Thanks so very much! I never observed that. Thanks a lot Jan Honza!
> Regards,
> Shreyas
> On Thu, Aug 2, 2012 at 1:15 PM, Jan Honza Odvarko <odva...@gmail.com> wrote:
> > On Aug 2, 9:01 am, Shreyas Agasthya <shreya...@gmail.com> wrote:
> > > Guys,
> > > Great product! However, how do I change the hot-keys in my 10.7.4 Mac
> > > running the latest FIREFOX. I want to change the hot key combination of a
> > > few controls. In dire need.
> > Firebug (icon) menu -> Customize Shortcuts
> > opens a dialog to customize shortcuts.
> > Does it help?
> > Honza
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Firebug" group.
> > To post to this group, send email to firebug@googlegroups.com
> > To unsubscribe from this group, send email to
> > firebug+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >https://groups.google.com/forum/#!forum/firebug
It is apalling! Please help, I need to be able to use Firebug in web development, otherwise, Firefox can go the way of Netscape and IE. I will stick with Chrome. Unfortunately, Firefox is still out there and used by a good proportion of the world's population.
> <https://lh6.googleusercontent.com/-fJ3J-JdCNRE/UCuuMyLDsHI/AAAAAAAAAm...> Adobe
> has taken over my Firebug plugin and I am livid! I've tried everything from
> uninstalling Firefox, to disabling any Adobe .ext or plugin, and still that
> button is dedicated to Adobe. The audacity!
> It is apalling! Please help, I need to be able to use Firebug in web
> development, otherwise, Firefox can go the way of Netscape and IE. I will
> stick with Chrome. Unfortunately, Firefox is still out there and used by a
> good proportion of the world's population.
> PLEASE HELP!
> My regards, Georgette
> On Friday, July 13, 2012 9:20:34 AM UTC-4, Jan Honza Odvarko wrote:
