Yes, I was thinking about the same, reported: https://github.com/firebug/firebug.next/issues/314
Honza On Wednesday, February 4, 2015 at 11:05:13 PM UTC+1, San wrote: > > I normally use the Firebug 2 debugger, but I've been comparing its > behavior to that of Chrome and to the built-in Firefox debugger (all on a > Mac, if that matters). > > One thing I've noticed is the difference in behavior when you mouse over a > variable in a line of code that's already been run. In Firebug 2, a little > box displays right above the item you're hovering, showing its current > value. This is great and I rely on it a lot. In Chrome, nothing shows when > I hover. In the Firefox built-in debugger, sometimes something shows the > value (plus often a lot of extraneous information), way off to one side so > I have to hunt around for it... but often nothing shows, or the hover box > gets "stuck" and won't update, or something. It's all too awkward to really > use. > > I haven't tried Firebug 3, but I hope its debugger hover behavior remains > about the same as in Firebug 2. If it becomes almost unusable like the > built-in Firefox debugger, that would be a huge step backward. > > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/38a49570-a480-416d-92ca-d306536474e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
