You can try it out today in any page you like. > Pausing the debugger suspends all events and timeouts in the page and spawns (In reply to Panos Astithas from comment #10) In this case it would be possible to have a button to allow resuming either overlaid on the page content or somewhere else. Yes, I would imagine that we could wire up F8 to pause the debugger even when on the inspector tab. > keyboard shortcut/right-click menu option on the relevant node.) > there was a solution for this that works in a similarly easy fashion (e.g. > pseudoclasses is substantially easier by comparison, and it would nice if > you're debugging a large codebase you didn't write. > Also it can take work to find where to put a breakpoint, especially if > (In reply to Brian Grinstead from comment #6) keyboard shortcut/right-click menu option on the relevant node.) Locking CSS pseudoclasses is substantially easier by comparison, and it would nice if there was a solution for this that works in a similarly easy fashion (e.g. > markup view could be a bit of work, but it would at least be possible.Īlso it can take work to find where to put a breakpoint, especially if you're debugging a large codebase you didn't write. > selection doesn't work, so getting to the DOM node you care about in the > The only other issue with being paused is that 'click to select' highlighter Subsequent mouseover/out don't fire, just the first one. > the desired state, but for some reason the mouseout event still fires as the > pause, then press ctrl+shift+c to flip to inspector, it *almost* gets into > debugger tab, hover the mouse over the JS Mouseover object, press F8 to

(In reply to Brian Grinstead from comment #6) The only other issue with being paused is that 'click to select' highlighter selection doesn't work, so getting to the DOM node you care about in the markup view could be a bit of work, but it would at least be possible. I noticed on the demo page:, that if I open inspector tab then debugger tab, hover the mouse over the JS Mouseover object, press F8 to pause, then press ctrl+shift+c to flip to inspector, it *almost* gets into the desired state, but for some reason the mouseout event still fires as the mouse leaves. > see CSS 'events' like :hover happening while debugging. > If you hit a breakpoint then I think you're roughly in this state. > arbitrary steps that are needed to get to the state you want to inspect, > keyboard shortcut to 'freeze' the DOM from receiving any more events, kind > This does get me thinking though, it would be interesting if there was some > (In reply to Brian Grinstead from comment #3) Then you could go through whatever your arbitrary steps that are needed to get to the state you want to inspect, freeze it, and do your inspection. This does get me thinking though, it would be interesting if there was some keyboard shortcut to 'freeze' the DOM from receiving any more events, kind of like taking a screenshot. I can think of a bunch of weird cases that could happen in this case - what would the coords on the mouse event come through as? What if you move your mouse up into the rest of the page content, would a mouseout have to fire immediately on the element as it entered a different element? What if the process of getting to your state is more complicated than firing single event, etc. To take just the mouseover / mouseout example, what could tooling provide to make this easier? Suppose there was an item on the dropdown to force a mouseover. In your case you could always use the markup view to force things how you want them (add the 'hover' class to the js element, or whatever), but I know that doesn't solve the more complicated problem. Yeah, I feel your pain - I've often had to go in and modify scripts to not remove classes on mouseout, remove a conditional in some callback, etc in order to get things in the state just as I want them to for inspection. > 'lock mouseover' option when selecting a node which will make debugging this > way, so I think it's quite a common use case. > the event but as soon as you mouseout from the element the style disappears With the JS one, you can manually trigger > able to lock the styles changed by the event the same way you can with CSS Thanks for responding :) It's not so much triggering the events, but being

Firefox html inspector shortcut