Open Bug 1453259 Opened 7 years ago Updated 2 years ago

MediaStreamTrack.getSettings() should report correct resolution for screen capture immediately after applyConstraints() resolves

Categories

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

60 Branch
enhancement

Tracking

()

People

(Reporter: pehrsons, Unassigned)

References

Details

Attachments

(1 file)

Currently the timing around applyConstraints() and getSettings() when there are no capabilities (like screen capture) looks like: - applyConstraints(newConstraints) - Select desiredDimensions from newConstraints (one or both of [width, height] may be 0) - Reconfigure capture with desiredDimensions (if this fails, reject applyConstraints() and early exit) - (settings.width, settings.height) = desiredDimensions - resolve applyConstraints() - frame comes in with actualDimensions - (settings.width, settings.height) = actualDimensions When applyConstraints resolves we need to guarantee that the settings are already correct.
Rank: 25
Priority: -- → P3

This bug affects me too. I attached a simple example. Just click the button and share your entire screen.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: