From 0a05da06e4ef685efcaa93180dccd660b699b194 Mon Sep 17 00:00:00 2001 From: cy-moi Date: Wed, 24 Jul 2024 10:24:07 +0200 Subject: [PATCH 1/9] Add iframe support explanation --- .../session_replay/browser/troubleshooting.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 677ac2c97a972..14067654e07bd 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -25,9 +25,12 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: -- The following HTML elements: `iframe`, `video`, `audio`, or `canvas` +- The following HTML elements: `iframe without srcDoc`, `video`, `audio`, or `canvas` + - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. While iFrames and their parent windows will appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not currently supported. + - The [Web Animations API][7] + Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. ### Fonts or images do not render properly From 9d2498b0768d9b5466e2a0a9cf5f14d2da72eff4 Mon Sep 17 00:00:00 2001 From: cy-moi Date: Wed, 24 Jul 2024 10:28:14 +0200 Subject: [PATCH 2/9] Avoid temporal wordings --- .../session_replay/browser/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 14067654e07bd..0aac61c38fb2e 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -26,7 +26,7 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: - The following HTML elements: `iframe without srcDoc`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. While iFrames and their parent windows will appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not currently supported. + - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. - The [Web Animations API][7] From 03e18ada631d1df81a9dc9d8d63103a85f16d52f Mon Sep 17 00:00:00 2001 From: cy-moi Date: Wed, 24 Jul 2024 10:28:57 +0200 Subject: [PATCH 3/9] Remove extra white space --- .../session_replay/browser/troubleshooting.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 0aac61c38fb2e..88ce816dfeacb 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -27,10 +27,8 @@ Session Replay does not support: - The following HTML elements: `iframe without srcDoc`, `video`, `audio`, or `canvas` - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. - - The [Web Animations API][7] - Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. ### Fonts or images do not render properly From f7c8df4fe8a4a2cd7f01ab14feabfd37793d055a Mon Sep 17 00:00:00 2001 From: cy-moi Date: Thu, 25 Jul 2024 14:06:37 +0200 Subject: [PATCH 4/9] Fix wording --- .../session_replay/browser/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 88ce816dfeacb..9a1fdc8d583b0 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -25,8 +25,8 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: -- The following HTML elements: `iframe without srcDoc`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. +- The following HTML elements: `iframe`, `video`, `audio`, or `canvas` + - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. - The [Web Animations API][7] Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. From b276d1b84eb414e263b83ed666c19f083b3c8779 Mon Sep 17 00:00:00 2001 From: cy-moi Date: Fri, 26 Jul 2024 09:17:43 +0200 Subject: [PATCH 5/9] Remove unnecessary mentions --- .../session_replay/browser/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 9a1fdc8d583b0..3fceb945e0eac 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -26,7 +26,7 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: - The following HTML elements: `iframe`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across domains, enable `usePartitionedCrossSiteSessionCookie: true` to ensure they are associated with the correct session. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. + - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. - The [Web Animations API][7] Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. From 72ee9b10ffc3af66f27e02086df9f87f6dbdfcd8 Mon Sep 17 00:00:00 2001 From: cy-moi Date: Fri, 26 Jul 2024 09:26:56 +0200 Subject: [PATCH 6/9] Fix wording --- .../session_replay/browser/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 3fceb945e0eac..8a1b6c1e81e76 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -26,7 +26,7 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: - The following HTML elements: `iframe`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, it's necessary to separately instrument the iFrame code. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. + - To render iFrames in Session Replay, you can separately instrument the iFrame code. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. - The [Web Animations API][7] Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. From 3e3ab588a2a69f3d31b98580b7a8885b63537a90 Mon Sep 17 00:00:00 2001 From: cy-moi Date: Fri, 26 Jul 2024 11:01:05 +0200 Subject: [PATCH 7/9] Fix wording --- .../session_replay/browser/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index 8a1b6c1e81e76..bc86e8e57a29c 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -26,7 +26,7 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: - The following HTML elements: `iframe`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, you can separately instrument the iFrame code. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as distinct entities within the same session, embedding iFrame replays directly into their parent windows is not supported. + - To render iFrames in Session Replay, you can separately instrument the iFrame code. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as separate pages within the same session, embedding iFrame replays directly into their parent windows is not supported. - The [Web Animations API][7] Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. From 2c93b9a34475ca2ccafa8fad6c24afa439ffb770 Mon Sep 17 00:00:00 2001 From: Cy Zheng Date: Mon, 29 Jul 2024 12:00:08 +0200 Subject: [PATCH 8/9] Update content/en/real_user_monitoring/session_replay/browser/troubleshooting.md Co-authored-by: Michael Cretzman <58786311+michaelcretzman@users.noreply.github.com> --- .../session_replay/browser/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index bc86e8e57a29c..a383adbbb6d91 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -26,7 +26,7 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: - The following HTML elements: `iframe`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, you can separately instrument the iFrame code. For iFrames that span across sub-domains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as separate pages within the same session, embedding iFrame replays directly into their parent windows is not supported. + - To render iFrames in Session Replay, you can separately instrument the iFrame code. For iFrames that span across subdomains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as separate pages within the same session. Embedding iFrame replays directly into their parent windows is not supported. - The [Web Animations API][7] Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements. From 40d038f2a99574fa47204eee433131f871b51620 Mon Sep 17 00:00:00 2001 From: cy-moi Date: Mon, 29 Jul 2024 16:30:37 +0200 Subject: [PATCH 9/9] Do not capitalize iframe --- .../session_replay/browser/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md index a383adbbb6d91..fc8084c06c384 100644 --- a/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md +++ b/content/en/real_user_monitoring/session_replay/browser/troubleshooting.md @@ -26,7 +26,7 @@ If you experience unexpected behavior with Datadog Session Replay, use this page Session Replay does not support: - The following HTML elements: `iframe`, `video`, `audio`, or `canvas` - - To render iFrames in Session Replay, you can separately instrument the iFrame code. For iFrames that span across subdomains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iFrames and their parent windows appear as separate pages within the same session. Embedding iFrame replays directly into their parent windows is not supported. + - To render iframes in Session Replay, you can separately instrument the iframe code. For iframes that span across subdomains, use `trackSessionAcrossSubdomains: true`. After correct instrumentation, iframes and their parent windows appear as separate pages within the same session. Embedding iframe replays directly into their parent windows is not supported. - The [Web Animations API][7] Session Replay requires you to use an HTTPS connection. If you aren't using a secure connection, the resources time out and you can't see images and some page elements.