Associate |origin| in PeerConnectionTrackerHost::GetUserMedia with RenderFrameHost
Reported by
vm.ar...@samsung.com,
Jan 15 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: Associate |origin| with |RenderFrameHost| object. What is the expected behavior? What went wrong? Associate |origin| with |RenderFrameHost| object Did this work before? N/A Chrome version: 63.0.3239.132 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Apr 26 2018
What does this bug consist of?
,
Jun 21 2018
Closing since it is not clear what this bug is. Please reopen if a clarification is provided.
,
Jun 26 2018
IIRC, this bug was created to remove passing origin as string [1] in PeerConnectionTrackerHost mojo ipc. Instead, RenderFrameHost should be used to get the origin on the browser side. [1] https://cs.chromium.org/chromium/src/content/common/media/peer_connection_tracker.mojom?l=33 Reopening this bug. I'll take up this one. guidou@: For a start, PeerConnectionTrackerHost has to be made per frame?
,
Jun 26 2018
c.padhi@: Thanks for taking care of this. PeerConnectionTrackerHost doesn't necessarily have to be per-frame because PeerConnectionTracker and other PeerConnection classes are per renderer process, not per frame. It's OK to make it per frame, but then the client-side PeerConnectionTracker should be made per frame as well. Note also that passing the origin to PCTH is not a serious problem since this origin is used only for informative purposes in chrome://webrtc-internals, and not to make authorization decisions based on it.
,
Jun 26 2018
Oh, okay. Thanks for the information though. Let's drop this bug then? |
||||
►
Sign in to add a comment |
||||
Comment 1 by guidou@chromium.org
, Jan 15 2018Owner: guidou@chromium.org
Status: Assigned (was: Unconfirmed)