You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider a track cropped-to cropTarget1. Assume a valid cropTarget2 is produced to match element2, then element2 is removed from the DOM and eventually garbage-collected. If we now call track.cropTo(cropTarget2), it would return a rejected promise. But what should happen with track? Should it keep issuing frames cropped to cropTarget1, or should it be muted?
(FWIW, Chrome's current behavior is that the track no longer issues new frames. Up for debate if that's desirable.)
The text was updated successfully, but these errors were encountered:
Consider a
track
cropped-tocropTarget1
. Assume a validcropTarget2
is produced to matchelement2
, thenelement2
is removed from the DOM and eventually garbage-collected. If we now calltrack.cropTo(cropTarget2)
, it would return a rejected promise. But what should happen withtrack
? Should it keep issuing frames cropped tocropTarget1
, or should it be muted?(FWIW, Chrome's current behavior is that the track no longer issues new frames. Up for debate if that's desirable.)
The text was updated successfully, but these errors were encountered: