-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mobile Replay]: Video disappears when pausing on Safari #82795
Comments
Scenarios that do and don't recreate the bug:
Note: When the page first loads this bug doesn't always happen, but after a few reloads it does. When looking at replays on Safari, it doesn't always happen, but when it does, the bug is pretty jarring since the video disappears.
Doesn't recreate the bug:
|
Next step:
Step 1 did not result in the bug being reproduced. I decided not to do exactly step 2, but I did something which had the same underlying idea of importing the video asynchronously instead since there was a lot of types and components which needed to be ported over to get Instead, I found that replacing My theory is that dynamically importing the file containing the video causes this bug, more investigation is needed to verify this. |
Sometimes when pausing a video replay on Safari, the video seems to disappear. Additionally, the video sometimes disappears after several seconds when it's not being played. When inspecting, video element is still there and it still has display:block but it's not visible. Changing the display attribute makes it visible again.
Screen.Recording.2024-12-31.at.3.32.33.PM.mov
This only happens on Safari and I've so far only seen it within the replays in the brustolin org. I've tested on a simple create react app and have not run into this bug. I have been able to reproduce this on Sentry stories with a third party video, so it seems like something within Sentry is causing this. Reducing down the Sentry storybook page until the video functions as normal should lead to the root cause of the bug.
The text was updated successfully, but these errors were encountered: