I agree that the shifting positions of the debugger panels makes some things more difficult to read at a glance. However, moving the Scope panel above the Call Stack panel only trades one problem for another. The Scope panel is variable height, just like the Call Stack panel, which will result in the position of the Call Stack shifting around depending on the current break point. I think it's safe to argue that for most people that keep both Call Stack and Scope open, it's more beneficial for the former to be stable.

Some workarounds for your current issue:

1. The Call Stack panel can be collapsed now. Perhaps while trying to isolate this issue, it would be easier to collapse the Call Stack panel temporarily so it doesn't affect the Scope panel's position.

2. If there's a particular variable or field you're tracking, perhaps adding a watch on the variable (https://goo.gl/5Dl8E6). Watched variable appear at the top of the debugger and won't change position as you step through code.

3. If you're trying to catch when a particular object/field changes in a way that can specified as a condition (e.g. when foo.bar != 0), you could use a conditional breakpoint (https://goo.gl/NfCsiy). Unfortunately, there's no way currently to break when a variable's value changes arbitrarily.

Longer term, we are exploring making some of these panels a fixed-but-adjustable height. This will ensure they're always in a predictable position. The largest barrier to this now is when DevTools is docked to the bottom of the window, or otherwise has limited height to distribute between these panels.