Open Bug 1306034 Opened 9 years ago Updated 2 months ago

Implement aspectRatio constraint for cameras

Categories

(Core :: WebRTC: Audio/Video, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: jib, Unassigned)

References

()

Details

(Keywords: parity-chrome, parity-safari, Whiteboard: webcompat:risk-moderate )

User Story

https://mozilla-hub.atlassian.net/browse/FFXP-677
The spec (see URL) defines an aspectRatio constraint we should implement. It would help give a fitness distance boost to modes that fit a site's preferred aspect ratio, as well as limit modes to an aspect ration with min/max/exact.
Rank: 23
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Any idea when will this be available in Firefox.
Type: defect → task

Is there any plan to implement the aspectRatio constraint?

All major browsers have supported this for at least 4 years, but in Firefox it is necessary to go through a hardcoded list of resolutions if you need a specific ratio. The constraint would be really helpful.

Type: task → enhancement
Severity: normal → S3

Chrome and Safari will now both support aspectRatio on MediaStreamTrack as of WebKit preview 171.

Whiteboard: webcompat:risk-moderate
User Story: (updated)
No longer blocks: webrtc-triage
User Story: (updated)
See Also: → 1978789

With Firefox now supporting "crop-and-scale" (bug 1286945), having this constraint is more pressing. Up-prioritizing.

This gUM demo shows one way to preserve aspect ratio is to only constrain on width OR height. But e.g. on macOS if constrained only on height, there's a risk of ending up with a vertical mode (like 1080x1920). aspectRatio would help here.

ofc websites that constrain both width and height don't have this problem but still.

Priority: P3 → P2
User Story: (updated)
You need to log in before you can comment on or make changes to this bug.