I also reported this to Roboform last week along with a screencast and received the following reply: --- Ilya replied (2011/08/27 02:14 am EDT): We are sorry, but the problem you are reporting is known to us. We are working on the solution to it, but there is still no ETA when it will be fixed. ---
I am losing hope that this problem is going to be resolved anytime soon. - eric On Aug 23, 12:57 pm, Eyesi <[email protected]> wrote: > I hope that this problem can be resolved soon. It must be Firebug > that's causing the problem because out of the three applications > mentioned FF5 andRoboform7.3.2 everything was working fine with > Firebug 1.7.3 and it broke when it changed to 1.8.0. I don't think the > later revisions of FF andRoboformchanged anything. > > I really can't live withoutRoboformso I have to give that addon > priority in my main browser. However, my temporary solution is to run > Firebug in Google Chrome - I use it mainly to inspect and experiment > with css elements, so it's a reasonable work-around for that purpose. > > On Aug 23, 5:28 pm, Brian Tippets <[email protected]> wrote: > > > > > > > > > While that is a workaround of sorts, it's more or less just disabling > >Roboform; or at least the most useful part of it. -- 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.
