Skip to content

Commit f3f046f

Browse files
committed
fix(browser): improved language of troubleshooting section
1 parent f26f785 commit f3f046f

File tree

1 file changed

+14
-13
lines changed

1 file changed

+14
-13
lines changed

src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx

+14-13
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: "Session replay"
33
metaDescription: "Play back user interactions to debug faster and improve page performance."
4-
freshnessValidatedDate: 2024-04-23
4+
freshnessValidatedDate: 2024-11-11
55
---
66

7-
Session replay plays back user interactions on your web app and maps other telemetry data to help you understand your user's journeys. Session replay can be used for troubleshooting and improving the end-user experience, such as:
7+
Session replay captures interactions on your web app and maps other telemetry data to help you understand your user's journeys. Session replay can be used for troubleshooting and improving the end-user experience, such as:
88

99
* **Troubleshooting JavaScript errors**: Troubleshoot the cause of an error by seeing what the user was doing when the error occurred. For example, if an end user receives an error while trying to complete an ecommerce transaction, you can use session replay to see which steps they took and what data they entered before the error occurred. This can help you quickly identify and fix the root cause of the problem.
1010
* **Improving the user experience**: Discover areas of your web app that are causing users frustration. For example, you might see that users are getting lost in your navigation or clicking on buttons that don't do anything.
@@ -258,18 +258,19 @@ For more details on session replay, see the following sections:
258258
Session replay feature is enabled, but you're not seeing replay data for iframe content.
259259

260260
### Solution
261+
262+
The behavior of session replay in iframe scenarios depends on the origin of the iframe and the placement of the browser agent.
261263

262-
Assuming a web page consists of a top level window with a child iframe, here are some possible fixes:
263-
* If the iframe is **same-origin**,
264-
* agent placed in the top level will capture session replay events in both the window and the iframe.
265-
* agent placed in the iframe will capture events only in its own context.
266-
* agents placed in both window and iframe will each report session replay events independently (with their own session) in line with the two bullets above.
267-
* If the iframe is **cross-origin**,
268-
* agent placed in the top level will only capture session replay events in the window; iframe will appear blank.
269-
* agent placed in the iframe will only capture events in the iframe.
270-
* if *recordCrossOriginIframes* is not enabled (current state of agent) in the replay options, agents placed in both window and iframe will each report session replay events independently (with their own session) in line with the two bullets above.
271-
* if *recordCrossOriginIframes* <u>is</u> enabled and agents are in both window and iframe, the iframe agent does <u>not</u> report session replay events. However, the window agent will report events with the cross-origin iframe events captured in replay.
272-
* Please note, session replay is not compatible with <frame> elements and this is unsupported.
264+
Assuming a web page consists of a top-level window with a child iframe, here are some possible fixes:
265+
* **Same-origin iframes**:
266+
* If you place the browser agent in the top-level window, session replay captures both the window and the iframe.
267+
* If you place the browser agent in the iframe, session replay only captures what's in the iframe.
268+
* If you place the browser agent in both the top-level window and iframe, session replay captures what's happening independently in both the window and iframe, resulting in two separate sessions.
269+
* **Cross-origin iframes**:
270+
* If you place the browser agent in the top-level window, session replay only captures what's in the window. The iframe will appear blank in session replay.
271+
* If you place the browser agent in the top-level window, session replay only captures what's in the iframe.
272+
273+
Session replay is **not** compatible with <frame> elements.
273274

274275
</Collapser>
275276
</CollapserGroup>

0 commit comments

Comments
 (0)