search

whatwg / html

HTML Standard
https://html.spec.whatwg.org/multipage/
Other
8.18k stars 2.71k forks source link

"media data processing steps list" is used for both responses and "raw data" #1525

Open annevk opened 8 years ago

annevk commented 8 years ago

I think it would be better if the network specific bits were handled before handing off to that algorithm. That would make fixing #158 easier. It seems there's only one invocation from the network side. Presumably that invocation is due to https://fetch.spec.whatwg.org/#process-response?

(Why is the label video and not media?)

foolip commented 8 years ago

(Why is the label video and not media?)

If I created the label, probably because media also means some other things in CSS land, and almost everything about video also applies to audio, except the named Audio() constructor I guess. Feel free to rename if you like though.

foolip commented 8 years ago

I have to say I've never properly understood how this stuff is supposed to work, and the structure of the algorithm doesn't match any implementation I've worked on. That being said, do you have an example I can study of how to properly integrate with Fetch, or is this issue more limited?

The linkage here is via "The networking task source tasks to process the data as it is being fetched must each immediately queue a task to run the first appropriate steps from the media data processing steps list below." I suppose there's a callback or concept to use instead?

Possibly complicating the picture is the "Whenever new data for the current media resource becomes available, queue a task to run the first appropriate steps from the media data processing steps list below." in the local mode, where Fetch isn't involved at all.

annevk commented 8 years ago

The issue is more limited iirc. Some checks only apply to responses and not raw data. So things need to move around a bit.