Fix: fix Android chrome mobile not rendering html <video> element #1938
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
force position html video element on top left so it stays on screen and thus is rendered by chrome mobile
dganzella
changed the title
dganzella
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is an issue in chrome mobile where, if the video element tag is outside of the visible viewport, the video won't be rendered (will appear as black).
That can happen if the added video tag just happens to go in the bottom of a body, and whatever relative elements exists before pushes it outside of the viewport boundary
Screen.Recording.2025-10-03.at.20.39.21.mov
This fix forces the position html video element (that is already an absoltue element) to be on the top left so it stays on screen and thus is rendered by chrome mobile not depending of the contents of the html itself.
I've tested this and it only happens specifically in Androrid-Chrome combo
cc @kNoAPP that helped find where in the code the html element was created