search

PostHog / posthog

🦔 PostHog provides open-source web & product analytics, session recording, feature flagging and A/B testing that you can self-host. Get started - free.
https://posthog.com
Other
21.84k stars 1.3k forks source link

Display uncapturable elements with special rendering #12564

Open benjackwhite opened 2 years ago

benjackwhite commented 2 years ago

Is your feature request related to a problem?

Certain elements of the page we are unable to capture such as iframes or WebGL.

Describe the solution you'd like

Instead of showing it in a blank state, we should render some custom CSS to indicate that it is un-renderable and perhaps have a little info indicator to explain in app why this can't be rendered. This would help prevent confusion as to whether their website has an issue or whether it is just a limitation of the recorder.

Describe alternatives you've considered

Additional context

Big up the community for the suggestion 🙌 https://posthogusers.slack.com/archives/C01GLBKHKQT/p1667323077866229?thread_ts=1667322637.489749&cid=C01GLBKHKQT

Thank you for your feature request – we love each and every one!

pauldambra commented 7 months ago

another case for this is if we drop a message because it is too large we could insert a custom event to say that we dropped it, how big it was to make debugging easier - in the case of dropping all full snapshots in a recording we could insert a full snapshot explaining the issue

marandaneto commented 7 months ago

Btw this is not a JS-SDK issue but rather ingestion, the elements were captured but they most likely exceeded our limits so they had to be dropped. This can lead to a broken recording either from the beginning (full snapshot) - white screen or a single node that breaks the recording at certain points.

The solution for both problems is probably the same solution hence a single issue.