bd0dfa17cc
The media monitor responsible for triggering the reconnecting view in the screen sharing component was maintaing the previous state (eg flowing) in cases where the peer just failed before media stopped flowing. That triggered an error in the bps calculations that caused the previous state to be preserved - eg stuck in flowing while it should be not_flowing. These changes make it so that if there's not peer to fetch stats from, them the bps calculations will correctly return 0 (which translates to not_flowing). |
||
|---|---|---|
| .. | ||
| switch-button | ||
| component.jsx | ||
| container.jsx | ||
| service.js | ||
| styles.js | ||