Closed pauldambra closed 6 months ago
Hide Explore DOM feature, we have virtual views, this won't make sense for Mobile
I'm going to add a note when a recording is mobile for any portion and then we can also add the view tree as an option.
While we won't offer it, someone could pass session id from mobile app to website and stitch a recording between device types, in a similar way to cookies allowing cross sub-domain recording. So, it'll be trickier but we should anticipate things working for web, mobile, or web+mobile recordings
More like a question, since we have synthetic IDs, what if the removed/updated wireframe is a synthetic ID? Would that work the way how it is implemented? I believe the synthetic IDs are just the nested components right?
For example, a button on Mobile is a div and a nested text, if I remove or update the button, is the whole div and text correctly mutated?
from https://github.com/PostHog/posthog/pull/19567#issuecomment-1875030166
For now I'm hoping this works without much effort but we will need to review to make sure that we're tagging the ID at the right level so that clean-up works. Or be able to walk the DOM tree to clean up synthetic nodes periodically too
we started getting user feedback.... let's have a follow-up kilo issue for release
One smaller than Mega is Kilo 🏋️
This issue acts as a tracking place of the to-do list to get Mobile replay ready for beta release
What's the minimum we can add so we can start getting real user feedback
href
) always leads toRecording not found
FE Config (stretch)
Needed but probably don't block...
See also: