Actually issue 2852 describes some advanced parsing of the values, which need to be addressed differently. Therefore I created issue 7484<https://code.google.com/p/fbug/issues/detail?id=7484>, which covers restoring the functionality of Firebug 1.12.
Sebastian On Wednesday, May 28, 2014 11:55:13 PM UTC+2, Sebastian Zartner wrote: > > That's a bug, which is already reported as issue > 2852<https://code.google.com/p/fbug/issues/detail?id=2852>. > Your test case and the test case attached there work fine for me using FF > 29.0.1 + FB 1.12.8 on Win8.1, though fail on FF 32.0a1 + FB 2.0b7. > > Sebastian > > On Wednesday, May 28, 2014 11:01:11 PM UTC+2, alfonsoml wrote: >> >> This is a simple demo available at >> http://jsbin.com/xeminufa/1 >> >> <input type="button" onclick="test()" value="Open Firebug and click me"> >> <script> >> function test() >> { >> var obj = {} >> >> obj.name = "this is a test"; >> >> debugger; >> // Now mouse over obj.name and it will show an empty string as the >> tooltip. >> >> obj.otherValue="this doesn't show at all" >> debugger; >> // this one doesn't even show a tooltip >> } >> </script> >> >> >> Putting the cursor over obj.name shows an empty tooltip giving the false >> impression that the value is an empty string. obj.otherValue on the other >> side doesn't show anything at all. >> >> I thing that this kinds of things used to work previously. >> >> Tested with Aurora 31.0a2 (2014-05-27) on Windows 7 and Firebug 2.07b >> >> Am I wrong or is this a bug? >> > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to firebug@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/1d7841a3-1057-4ce5-b7b3-be5756fa5a01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
