Videos with border radius have become inverted upside down on Android (Mali G-77)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox151 | --- | unaffected |
| firefox152 | --- | unaffected |
| firefox153 | --- | affected |
People
(Reporter: ke5trel, Unassigned, NeedInfo)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(3 files)
STR:
- Launch latest Android Nightly 153.0a1 on Samsung S20 (Mali G-77).
- Visit example test case of video element with
border-radius.
Expected:
Video appears upright like before.
Actual:
Video is upside down. Removing border-radius makes the video upright.
Does not happen with layers.acceleration.disabled = true.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f2d0991acbafc6586af872f06f957b6210468773&tochange=a5cce613683a4e9794329147f83d0eefb909f799
Possibly regressed by Bug 2038650.
Comment 2•2 days ago
|
||
:nical, since you are the author of the regressor, bug 2038650, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Adreno 710 has similar issues as well: images, gifs and videos appear upside down and flipped horizontally.
It might be some kind of initialization thing though only reproducible on cold start. When the same site is loaded again into a tab of a running Nightly, its image/video orientations are correct.
@Walter this appears even when loading from non-fresh loading. All videos with a border radius using native video embeds have this issue, this includes tumblr, bsky, etc and happens regardless of initialization loads of the application.
Comment 5•2 hours ago
|
||
I can reproduce this on a Pixel 10 Pro XL and a Pixel 6a, with the video embedded in this bugzilla comment (as viewed on the bugzilla bug-report page itself):
https://bugzilla.mozilla.org/show_bug.cgi?id=2043936#c1
Ran across this bug when tracking down a regression range (and finding bug 2038650 with this tracked as a regression).
Comment 6•1 hour ago
|
||
Description
•