New issue
Advanced search Search tips

Issue 903721 link

Starred by 3 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Webrtc webkitrtcpeerconnection not working after update to 70

Reported by pavan.cs...@gmail.com, Nov 9

Issue description

Chrome Version       : <70.0.3538.80>
URLs (if applicable) :
Other browsers tested:Microsoft Edge:FAIL (40)
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: PASS/FAIL (Version)
    Firefox: PASS/FAIL (Version)
       Edge: PASS/FAIL (Version)

What steps will reproduce the problem?
(1)Have a javascript code which reads private ip of the client, which used to work on chrome 69
(2)
(3)

What is the expected result?
Rtcpeerconnection object was instantiated and used to read the clients ip address 

What happens instead?
Rtcpeerconnection is no longer instantiable 

Please provide any additional information below. Attach a screenshot if
possible.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Components: Blink>WebRTC
Labels: Needs-Triage-M70
what do you mean by "not instantiable"? What call fails, and with what error?

Note that the "webkit" prefix has been obsolete for years.

Cc: hbos@chromium.org
Components: -Blink>WebRTC Blink>WebRTC>PeerConnection
Labels: Needs-Feedback

Sign in to add a comment