In a webrtc call, after the loadedmetadata event on the remote video element, the videoWidth and videoHeight properties are incorrect.

By design Issue #12143024

Details

Author
Steve K.
Created
May 26, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.15063
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

To reproduce, visit https://webrtc.github.io/samples/src/content/peerconnection/pc1/ in Edge and open the console.

Clicking Start will log the local videoWidth and videoHeight correctly

Clicking Call will log both the remote videoWidth and videoHeight as 6px.

In a range of tests, and in the product I am working on these properties always have the value of 6px.

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce a problem in Edge with the information at hand.

    What is the correct local video width and height in px? Edge says local is 640x480 and remote is 6x6, but Chrome says local is 2x2 and remote is 2x2.

    Please update this case with the requested information and perhaps a screenshot of the incorrect and correct logs.

    Best Wishes,
    The MS Edge Team

  • In this case, the remote should match the local (640x480) - see http://w3c.github.io/html/semantics-embedded-content.html#the-video-element

    I’ve attached screenshots from Edge (15), Chrome (58) and Firefox (53) on Windows 10 - I get the same results with the same versions of Chrome and Firefox on MacOS.

    (Please note Chrome will produce no video and report 2x2 when another browser has control of the webcam)

  • Microsoft Edge Team

    Changed Assigned To to “Travis L.”

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Frank L.”

    Changed Status to “By design”

  • Thanks Steve for sharing the observation with us!

    When the mediaStream object on the remote side is attached to the srcObject of the video tag, we internally set 6x6 as the initial video resolution so we could build up the media playback pipeline.  When the first video frame is actually received, we will update that on the video tag accordingly.  Other browser implementations might choose other initial values, e.g. 2x2, etc., which are all fair implementation decisions.  

    I’m resolving the issue as by-design.  But, please let us know if you have further question.

    All the Best, Shijun for the Edge team

You need to sign in to your Microsoft account to add a comment.

Sign in