A comprehensive description:

Currently the step button for debugging event sheets after hitting a breakpoint is tied to the game window. It would be a lot more convenient to also have a step button next to the preview button in the editor and a step key bind that would be available while the editor is in focus.

It solves a real problem:

This will help people who do not have multiple monitors or not a lot of screen real estate debug easier.

It covers alternatives and workarounds:

Currently the manual states, "Pressing Next will step to the next event, condition or action in sequence in the event sheet. Alternatively, press F10 with the browser window focused. This is useful for stepping through an event action-by-action and watching what happens in the debugger's inspector." This is useful when watching how the game operates, but it would be very convenient if this same functionality would be available in the editor when going through events to more easily determine what the game logic is doing.

Why the idea is important:

Debugging is an important part of making a game and this would greatly help in the speed and fluency of the debugging process for those using events.