Maintain call stack group expand/collapse states

[jasonLaster]

The challenge with maintaining expand/collapse states is that we'd want to do this with some knowledge of the stack.

One short term option is to allow disabling framework grouping

[jasonLaster]

This is similar to also maintaining expand/collapse states for scopes and objects which would also be hard without persistent object ids

[markerikson]

Is each step a different "pause point"? If not, we could tie the expanded value into the lifetime of the current pause point and reset when that changes. If each step is a different "pause", though, that won't work.

[jaril]

I'm down for disabling framework grouping altogether — saves us from a whole host of bugs and at worst keeps us at parity with chrome devtools.

[markerikson]

I'd certainly like to keep it if possible. I've always used Chrome for debugging, but that was one of the really neat things I liked about FF's DevTools.

[jasonLaster]

It's definitely a feature a lot of people enjoy which makes me reluctant to remove it outright

[jaril]

RIGHT — I hesitated writing that comment because I remembered @markerikson being wowed by it on the very first replay stream he did.

The only reason I remember is because you attributed it to work that "the replay team did" and in my head i was like…

[markerikson]

I did know that was in FF already :)

[jasonLaster]

oh snap - this already works.