Thanks for the suggestion. I've just started experimenting with Responsive Design View. I discovered very quickly two problems I'm having with it, although perhaps it's just my lack of familiarity with it.
The main problem is that some of my responsive design scripts, which normally (according to Firebug) fire only once when the page loads, have instead been firing twice when in Responsive Design View. (They all fire in the correct sequence, then they all fire again.) I can only guess why: I've been writing some very complex responsive scripts, and some of them respond not only to viewport size, but also to a user resizing the viewport after the page loads. This doesn't actually trigger a page reload, but does run the main responsive scripts again. (That would presumably be a desktop user, although a mobile user rotating their device might be similar.) Perhaps, even though I'm not switching to a different RDV preset after the page loads, there's a kind of implicit "page resize" that Firefox/RDV does behind the scenes during every page load, and that's triggering my "page resized" events?
That double-firing of the scripts would only be slightly annoying, but in addition, when I'm in RDV the Firebug console acts as though I had pressed "Persist" even though I haven't. In other words, my numerous console.logs, in addition to marching down the console -- twice -- continue to aggregate and quickly march down out of view in the console. I have to click and scroll the console (or click and clear it) to see them all every time I change the viewport size simulation... the console doesn't clear itself until I reload the page.
I'll continue to play with it a little more and see if there's any way around these issues... but RDV seems very simple. Are there options (for example, to clear the console automatically) that I'm not aware of?