+++ This bug was initially created as a clone of Bug #1759734 +++ (note I cloned the above bug about Firefox no longer respecting the `frameRate` constraint when passed by an application, to report a related symptom) What appears to have "regressed" at the same time is that the unconstrained frame rate produced by getDisplayMedia went *up*, from around ~22 fps of a youtube window on Windows 10 to ~30 fps. This is faster than Chrome (which is at around 17 fps). While this might sound good (whoo speed!) this discrepancy might have bad side effects, like use of more bandwidth, which could lead poorer degradation when available network bandwidth is low (causing symptoms like poor resolution compared to Chrome) since like frame rate can't be curbed anymore apparently. STRs are in bug 1760050 comment 3.
Bug 1760843 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
+++ This bug was initially created as a clone of Bug #1759734 +++ (note I cloned the above bug about Firefox no longer respecting the `frameRate` constraint when passed by an application, to report a related symptom) What appears to have "regressed" at the same time is that the unconstrained frame rate produced by getDisplayMedia went *up*, from around ~22 fps of a youtube window on Windows 10 to ~30 fps. This is faster than Chrome (which is at around 17 fps). While this might sound good (whoo speed!) this discrepancy might have bad side effects, like use of more bandwidth, which could lead poorer degradation when available network bandwidth is low (causing symptoms like poor resolution compared to Chrome) since frame rate can't be curbed anymore apparently. STRs are in bug 1760050 comment 3.