Open Bug 1848974 Opened 2 years ago Updated 7 months ago

getUserMedia: Displayed at -90 degrees in landscape orientation on Android 13

Categories

(Fenix :: Browser Engine, defect)

Firefox 116
All
Android
defect

Tracking

(firefox121 affected, firefox122 affected)

Tracking Status
firefox121 --- affected
firefox122 --- affected

People

(Reporter: kentagon906, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36

Steps to reproduce:

In landscape, open the page below and tap the "Open Camera" button.

https://webrtc.github.io/samples/src/content/getusermedia/gum/

Actual results:

Android 13 / Firefox 116.2.0 : The video is displayed at -90 degrees.

portrait: ok
landscape: ng

Android 13 / Firefox 118.0a1 : same result.

Android 13 / chrome 109: ok

Android 8 / Firefox 116.2.0: ok
Android 11 / Firefox 116.2.0: ok

Expected results:

In landscape, the rotation angle of the camera image should be adjusted.

The severity field is not set for this bug.
:jonalmeida, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jonalmeida942)

I wasn't able to reproduce this in the simulator. Can we still reproduce this in 120?

Severity: -- → S3
Component: General → Browser Engine
Flags: needinfo?(jonalmeida942) → qe-verify+

I was able to reproduce this issue on the latest Nightly 122.0a1 and also on Firefox 121.0 from 18.12.2023 with Samsung GalaxyZ Fold 4 (Android 13) and Google Pixel 7 Pro ( Android 14).

Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: qe-verify+
Blocks: 1874709

I can reproduce On Fairphone 5 (Android 13 firmware FP5.TT4H.A.162.20240609) with Firefox 128.0 and Firefox Nightly 130.0a1.

However I find it works correctly in the orientation in which the phone was when Firefox was started and break when rotated after startup. So if is started in Landscape orientation the video is wrongly rotated in portrait orientation.

You need to log in before you can comment on or make changes to this bug.