DevTools member here: We have a more powerful target switching (hidden) in the toolbar but are also working to better expose JS context switching early next year.

Debugger's new threads panel also solves this partially when you pause in a thread.

Are your use cases extensions, workers or iframes?

Thanks for all of your team's work! It's a critical tool that I love and use often.

My use case is more of, I saw something in the chrome tools that I didn't recognize from FF. I don't do much js debugging beyond console logging. But I'm starting a PWA project and will be making a service worker, so sounds like this functionality might be relevant.

ps - enjoyed this Changelog podcast w/ Jason Laster of the FF DevTools team, https://changelog.com/podcast/247.

This button on the top right is the closest you get, I think:

https://puu.sh/EMtaR/0f9c88cbd9.png

Oh, by "js contexts" do they mean "all the javascripts related to the page?" If so, then I guess this file tree-like explorer of js is the Firefox equivalent?

https://imgur.com/a/YvA9Hdw

No, each context can contain multiple scripts. Each browser tab has a single top-level context called 'top', plus it will have extra contexts for any frames or iframes within the page, as well as for any browser extensions running on the page.

Only script elements in the HTML of the top-level page (i.e. in the HTML served directly from the URL you see in the location bar) get to be in the 'top' context.