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
I thinked awhile about how expose TimeRangesstructures, they are particular arrays explaining how much has been played, how much is seekable, and buffered.
The specific properties are:
buffered
played
seekable
The abstraction i had in mind is to put all those 3 arrays to an array of hashes like this:
They are percentage-based and would couple well with an <input type="range"> element.
It's still under debate if it's worth to, or if there is a more clever/handy way to expose those informations
Comments are welcome
The text was updated successfully, but these errors were encountered:
After consideration, this functionality seems to not add value, people using those structures will be usually experts that have read the MDN estensively so can convert the values to percentage by themselves.
As another point, make the library convert the values to percentages will put a considerable overhead, because those structures have to be manipulated every time a progress/timeupdate event gets generated.
Is already possible and will be possible to access the raw structures from your angular application, without Scope automagic binding.
I thinked awhile about how expose
TimeRanges
structures, they are particular arrays explaining how much has been played, how much is seekable, and buffered.The specific properties are:
buffered
played
seekable
The abstraction i had in mind is to put all those 3 arrays to an array of hashes like this:
They are percentage-based and would couple well with an
<input type="range">
element.It's still under debate if it's worth to, or if there is a more clever/handy way to expose those informations
Comments are welcome
The text was updated successfully, but these errors were encountered: