> > Just read through the bug reports. I'm glad it's reported and appreciate > the complexity of the task. It pains me that the work-around is using > Chrome. I poked around their Inspector > code<http://www.google.com/codesearch/p#OAMlx_jo-ck/src/third_party/WebKit/Source/WebCore/inspector/front-end/>for > a bit but didn't find anything. > > I guess you could close version 1.9 without fixing this bug as it relates > to a firefox bug. Waiting for firefox 12 is however an unfortunate reality > IMHO. > As described in the issues we can just fix issue 4416<http://code.google.com/p/fbug/issues/detail?id=4416>and issue 2273 <http://code.google.com/p/fbug/issues/detail?id=2273> as soon as Firefox exposes the right API <https://bugzil.la/626359>, which is still not implemented. So we can't say yet, in which Firebug version these will be fixed, but it definitely won't be 1.9.
Sebastian -- 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 https://groups.google.com/forum/#!forum/firebug
