Bugzilla

(In reply to Alfred from comment #0)
> Actual results:
> 
> When I click the "play" symbol on the video, after a few seconds the "the quota has been exceeded" message appears on top of the video frame. The play symbol is replaced by an X surrounded by the "loading" animation. Nothing else happens from that moment on.

I tried and for me it shows "the quota has been exceeded" right away once clicked on the video. Did the video start for you?

I disabled "Enhanced Tracking Protection" (as there were some hints about blocked cookies in the console), but no luck.

I am able to see other Videos on that site, as well as the demo on https://videojs.com/ which seems to be the used player here. I have no idea what makes this video special.

From the code it looks as if we'd use [`NS_ERROR_DOM_QUOTA_EXCEEDED_ERR`](https://searchfox.org/mozilla-central/search?q=NS_ERROR_DOM_QUOTA_EXCEEDED_ERR&path=&case=false&regexp=false) in quite some media related places in order to signal large/invalid buffer values or such. Is that actually wanted? It looks confusing (I do not know, if some of those is what we see here).

(In reply to Alfred from comment #0)
> Actual results:
> 
> When I click the "play" symbol on the video, after a few seconds the "the quota has been exceeded" message appears on top of the video frame. The play symbol is replaced by an X surrounded by the "loading" animation. Nothing else happens from that moment on.

I tried and for me it shows "the quota has been exceeded" right away once clicked on the video. Did the video start for you?

I disabled "Enhanced Tracking Protection" (as there were some hints about blocked cookies in the console), but no luck.

I am able to see other Videos on that site, as well as the demo on https://videojs.com/ which seems to be the used player here. I have no idea what makes this video special.

From the code it looks as if we'd use [`NS_ERROR_DOM_QUOTA_EXCEEDED_ERR`](https://searchfox.org/mozilla-central/search?q=NS_ERROR_DOM_QUOTA_EXCEEDED_ERR&path=&case=false&regexp=false) in quite some media related places in order to signal large/invalid buffer values or such. Is that actually wanted? It looks confusing (I do not know, if some of those is what we see here).

Edit: From https://www.w3.org/TR/media-source-2/ it seems we must expect `QuotaExceededError ` not only from storage APIs. And from [the error definitions](https://searchfox.org/mozilla-central/rev/065102493dfc49234120c37fc6a334a5b1d86d9e/dom/base/domerr.msg#29,58,108) I understand we can have different error messages. Filing a bug.