Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 2 commits
- 2 files changed
- 2 contributors
Commits on Oct 3, 2025
-
fix: clip hard edge on web's rtc_video_view (#1936)
This PR fixes an issue where iOS Safari video box renders would exceed the boundaries set by the `RTCVideoViewObjectFit.RTCVideoViewObjectFitContain` and `RTCVideoViewObjectFit.RTCVideoViewObjectFitCover` guidelines. In the following examples (iOS Safari), I have specified the following: ```dart rtc.RTCVideoView( _renderer! as rtc.RTCVideoRenderer, mirror: true, filterQuality: FilterQuality.medium, objectFit: RTCVideoViewObjectFit.RTCVideoViewObjectFitCover, ); ``` **Before this PR**   **After this PR**  
Commits on Oct 7, 2025
-
Fix: fix Android chrome mobile not rendering html <video> element (#1938
) 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 https://github.com/user-attachments/assets/a0ef4506-7642-4fbd-a68e-dfc0d3798d5c 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
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.2.0...main