Currently the way in which different parts of a media resource are fetched is not specified in details, but is rather left to implementation. However, RT reporting for media exposes the different range requests, making this detail observable to web developers, even if the media is cross-origin (though every range request would only have the start/end in that case).
This is not necessarily a problem - but does exposing this detail have unintended consequences, such as a fingerprinting vector or exposing unintended info about cross-origin media?
Currently the way in which different parts of a media resource are fetched is not specified in details, but is rather left to implementation. However, RT reporting for media exposes the different range requests, making this detail observable to web developers, even if the media is cross-origin (though every range request would only have the start/end in that case).
This is not necessarily a problem - but does exposing this detail have unintended consequences, such as a fingerprinting vector or exposing unintended info about cross-origin media?
This came up from specifying media RT reporting