By doing a quick check, I didn't find anything suspicious in this profile yet. The decoding time is fast enough in average for 60fps video by checking the markers (via [extension](https://github.com/padenot/fx-profiler-audio-cb)), and the ratio of dropped frames is very little, which shouldn't make Youtube think that the user's computer is not strong enough. Youtube started adding a new buffer for lower resolution video at around ~65.3s, which is triggered by an event handler. But I checked the dom event around that range, I didn't find media element sending any suspicious event, just some normal ones (eg. timeupdate)
Bug 1776850 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
By doing a quick check, I didn't find anything suspicious in this profile yet. The decoding time is fast enough in average for 60fps video by checking the markers (via [extension](https://github.com/padenot/fx-profiler-audio-cb)), and the ratio of dropped frames is very little, which shouldn't make Youtube think that the user's computer is not strong enough. Youtube started adding a new buffer for lower resolution video at ~65.3s, which was triggered by an event handler. But I checked the dom event around that range, I didn't find media element sending any suspicious event, just some normal ones (eg. timeupdate)