1 Commits (c1f1c0d341500856a217530f7e4b144d5b0b85fe)

Author	SHA1	Message	Date
Robert Pintilii	c1f1c0d341	ref(TS) Convert some components to TS (#13179)	2 years ago
Robert Pintilii	754f658489	ref(redux) Remove connect wrapper (#13083)	2 years ago
Saúl Ibarra Corretgé	162a67fe8b	chore(lint) tame the (uppdated) linter	4 years ago
Hristo Terezov	f50872285d	ref(Filmstrip): Use Thumbnail component.	4 years ago
Bettenbuk Zoltan	0598e7369b	ref: eslint-config-jitsi@1.0.3	5 years ago
George Politis	d210f2f2e7	Adds a noAutoPlayVideo configuration option (used in testing). (#4714) ... This adds an option to disable video autoplay that will be used mostly with maleus (our selenium-based load testing tool for testing the new bridge). Disabling video rendering lowers the resource utilisation of the selenium nodes.	6 years ago
Bettenbuk Zoltan	2a5adfc601	Remove some Flow annotations	6 years ago
Saúl Ibarra Corretgé	c025c7e132	flow: tame the beast ... 🔥🔥🔥	6 years ago
Leonard Kim	486e8e35d9	ref: move all prop type declaration to flow ... For the most part the changes are taking the "static propTypes" declaration off of components and declaring them as Flow types. Sometimes to support flow some method signatures had to be added. There are some exceptions in which more had to be done to tame the beast: - AbstractVideoTrack: put in additional truthy checks for videoTrack. - Video: add truthy checks for the _videoElement ref. - shouldRenderVideoTrack function: Some component could pass null for the videoTrack argument and Flow wanted that called out explicitly. - DisplayName: Add a truthy check for the input ref before acting on it. - NumbersList: Move array checks inline for Flow to comprehend array methods could be called. Add type checks in the Object.entries loop as the value is assumed to be a mixed type by Flow. - AbstractToolbarButton: add additional truthy check for passed in type.	7 years ago
Lyubo Marinov	2e2129fa44	Import PropTypes from prop-types ... Prepare for React 16.	8 years ago
Leonard Kim	f3783efc48	squash: remove unused prop, update comment	8 years ago
Leonard Kim	1e84f993b4	fix(device-selection): use non-connect video preview ... Filmstrip only mode displays a device selection dialog that does not have access to the redux/connect. However, the current VideoTrack extends from AbstractVideoTrack, which assumes a redux connection. The fix is to move video display logic into a separate component and have device selection use that, while the existing VideoTrack remains connected to redux but uses the new video display component.	8 years ago
virtuacoplenny	244de8096f	feat(local-video): convert to react (#1705) ... * feat(local-video): convert to react - Create a VideoTrack component for displaying a video element. This mirrors native also having a VideoTrack component. - The VideoTrack component does not let React update it to prevent the video element from re-rendering, which could cause flickers and would not work with temasys's overriding of the video element. - VideoTrack extends AbstractVideoTrack to mirror native implementation and to get the dispatch of the onplaying event. - Remove the onclick handler on the video element. Honestly, I didn't get it to work, and did not try, but it is also unnecessary because another handler already exists on the video wrapper. * ref(device-selection): VideoInputPreview uses VideoTrack to show video * squash into conversion: change css selectors * squash into conversion: mix in abstract props * squash into conversion: change shouldComponentUpdate check * squash: update comment about why triggerOnPlayingUpdate is used	8 years ago
Lyubomir Marinov	7f3ff13c18	Merge jitsi-meet-react's mobile support ... As a step toward merging jitsi-meet-react with jitsi-meet to share as much source code as possible between mobile and Web, merge the part of jitsi-meet-react's source tree which supports mobile inside the jitsi-meet source tree and leave jitsi-meet-react's Web support in the source code revision history but don't have it in master anymore because it's different from jitsi-meet's Web support. In other words, the two projects are mechanically merged at the file level and don't really share source code between mobile and Web.	9 years ago
Lyubomir Marinov	d55e0f70d9	Import jitsi/jitsi-meet-react#2f23d98 ... As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at 2f23d98424 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.	9 years ago