On May 30, 5:53 am, Mike Ratcliffe <[email protected]> wrote: > I couldn't find any similar issues but I have created an issue with a > clear test case at:http://code.google.com/p/fbug/issues/detail?id=3112 > > In a nutshell, it would be useful to be able to freeze events and then > continue inspecting.
I am able freeze this case, but I have to set Firebug to break-on-next Javascript. The example issues mclose() even if the events are suspended. So the user experience is: 1. begin inspect, 2. mouse over button, menu shows up, 3. Control-Shift-f Menu frozen 4. move mouse toward Firebug, breakpoint hits on onmouseout Page is frozen, Firebug is on Script panel, you can use Firebug to see the DOM. You can't continue inspecting, because the events are needed to run the inspector. As a side effect, this 'feature' would allow you to trigger break on next by key board command. But the feature has a lot of issues: 1) breaking into Script panel is unexpected, 2) no inspect 3) interaction with breakpoints will have to be studied. > > Chris, does the issue I logged match your problem? I'm confused because the test case in 3112 does not seem to have anything to do with 'hover'. jjb > > On May 30, 7:26 am, Garrett Smith <[email protected]> wrote: > > > On 5/29/10, John J Barton <[email protected]> wrote: > > > > Overall this sounds like issue 2638. > > >http://code.google.com/p/fbug/issues/detail?id=2638 > > > No, that looks totally different. > > > THe OP wants to inspect an element while the cursor is over it. > > > THe problem is that you can't do that; once you right click, and mover > > the cursor down to the "Insepct Element", the mouseout fires or the > > element loses its hover state. > > > Garrett -- 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.
