Replies: 4 comments
-
I had originally picked this up for this week, starting with #3994 as a precursor. After talking with @jonbell-lot23 I'm going to punt on implementing this for right now. Jon's concerns are centered around losing the mapping of 1:1 between user events and elements in the Events Timeline. It's a trade-off between verbosity and clarity. Our current view is extremely clear, at the expense of being very verbose. I suspect that we might be able to take some inspiration from a directory structure to make this more manageable, so for a user who typed "Hello" they might see:
This might allow the Replay user to drill down into the specific "Key Up on |
Beta Was this translation helpful? Give feedback.
-
Nice I think some form of tree view makes sense in the future. Today, it's probably fine to just simplify what we're showing the user while keeping it literal. I think we just need a subset of the events we show now. For instance, I think it's fine to pluck the first of n events so the user seeks Down the line we can abstract it more and more so it's easier to follow |
Beta Was this translation helpful? Give feedback.
-
I agree with everything Jason just said |
Beta Was this translation helpful? Give feedback.
-
Moving to a discussion since this is not something we will implement right now and it will be nice to get more thoughts from the community |
Beta Was this translation helpful? Give feedback.
-
Follow up from #3307.
Add heuristics for collapsing keyboard events that should be together. Instead of having
Key Press H
andKey Press I
, there should be some logic that realizes that perhaps the user was typing something and it should be presented asTyped HI
.Beta Was this translation helpful? Give feedback.
All reactions