Skip to content

Conversation

bzang
Copy link
Contributor

@bzang bzang commented Apr 3, 2017

With createObjectURL losing support for media streams, we've created a work around for the react video element to support a srcObject

@bzang bzang requested review from adamweeks and ianwremmel April 3, 2017 15:35
el.srcObject = srcObject;
}
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have to do this because React strips out all non-whitelisted props. Currently srcObject is not allowed

@adamweeks
Copy link
Collaborator

We should track this as well: facebook/react#9146

src={src}
/>
);
}

Video.propTypes = {
audioMuted: PropTypes.bool,
src: PropTypes.string.isRequired
src: PropTypes.string,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we get rid of src entirely?

@@ -75,7 +77,8 @@ export default function reducer(state = initialState, action) {
const mediaState = {
localAudioDirection: call.localAudioDirection,
localVideoDirection: call.localVideoDirection,
localMediaStreamUrl: call.localMediaStreamUrl
localMediaStreamUrl: call.localMediaStreamUrl,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we stop using the url fields entirely?

toPersonAvatar,
toPersonName
}) {
const connectedClass = remoteMediaStreamUrl && styles.callConnected;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we still storing the remote/local media stream url if we're not using it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants