Well, according the post i linked to, the last comment was instructing the reporter to get some debugging, which I was hoping would happen. But, that was awhile ago, so it does appear that nothing will happen on that. I will see if i can get a public site to have this issue on.
On Aug 21, 11:55 am, johnjbarton <[email protected]> wrote: > On Aug 21, 8:03 am, Prefontim <[email protected]> wrote: > > > I second you on that motion. In fact, I am still using FF 3.0.x until > > Firebug 1.4 becomes more stabile. > > > Here is a post on the issue i'm am waiting on a fix for: > > >http://groups.google.com/group/firebug/browse_thread/thread/8814098b7... > > But you are linking to a newsgroup posting with a bunch of confusing > comments all mixed together. No one is reading that thread; no one is > working to fix any problem discussed there. > > If you want to get a fix for your problem you need to work with us to > reproduce the problem on our machines. We cannot see your problem from > over here. We don't know what the problem is. We are not working on a > fix, because we don't know of any problem to fix. > > Here is the bug report list:http://code.google.com/p/fbug/issues/list > > jjb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
