You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When processing a Replay we have DOM and other relevant data that can help us detect some errors.
This issue tracks ideas of Replay Issues we can create.
Related to the NextJS effort, hydration errors are currently filtered out by most orgs because they are not actionable (the only debugging context that we get comes from a console.error() message)
With replay we can see the before/after state of the page when that hydration error happened, thus make the error actionable by zooming in on the content that changed.
ryan953
changed the title
Replay: Detect and create issues using Replay data
[Epic] Replay: Detect and create issues using Replay data
Mar 13, 2023
ryan953
changed the title
[Epic] Replay: Detect and create issues using Replay data
[Epic] Replay: Replay Issues: or how i learned detect and create issues using replay data
Mar 22, 2023
ryan953
changed the title
[Epic] Replay: Replay Issues: or how i learned detect and create issues using replay data
[Epic] Replay: Replay Issues or how i learned detect and create issues using replay data
Mar 22, 2023
jas-kas
changed the title
[Epic] Replay: Replay Issues or how i learned detect and create issues using replay data
[Epic] Replay: Detect and create issues using Replay data
Mar 28, 2023
Uh oh!
There was an error while loading. Please reload this page.
Context
When processing a Replay we have DOM and other relevant data that can help us detect some errors.
This issue tracks ideas of Replay Issues we can create.
Detection Ideas
console.error()
message)<body>
has no nodes inside it (ignoring , <script> etc).<head>
element #67146The text was updated successfully, but these errors were encountered: