If there's a lot of message, expanding a group/stacktrace make the console scrolls to the bottom of the page, which can "hide" the group/stacktrace we want to see. When expanding a stacktrace, we should stay in the same place and see the stacktrace.
Also, I'm going to be testing using react-virtualized to help with performance. If that's the case, then the way we handle scrolling will be different.
As per the DevTools triage process doc , a P1 is defined as: - a security hole - causing data-loss - causing a crash - stopping the tools working - embarrassing Should be fixed within 24h and your manager should know about it and, between you, assign it to someone who can fix it. Maybe the "24h" part of this definition is a little too much and we should change it, but anyway, this does seem like a P1 and it should be assigned.  https://docs.google.com/document/d/1uG0foc0pphXJB489_8ClKjYr1wbRXeFyrkd_kIOv9ao/edit#
This is likely to be fixed with the perf work, so removing the P1 status.