- From: cynthia <notifications@github.com>
- Date: Tue, 06 Mar 2018 05:51:06 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 6 March 2018 13:51:29 UTC
> I believe the link is working. Maybe GH had troubles when you tried? It seems so - I just tried again and it works just fine. > I'm not entirely sure what you meant by this. Specifically, what you mean by "additional parsing from each application". I would expect web applications to copy-paste the type in their code or read it directly from a manifest of some sort. I imagined a use case where the content author wants to parse out just the codec and not the container information, with a string based format this would require parsing the string. > As mentioned below, only part 2 of the spec is something we are launching in Chrome. Part 3 is more draft-y and most of it was or will be merged into a CSS spec. This will likely be the case with the change event if it ever happens. It would be great if the spec could be trimmed down to only what is shipping. Stale draft material tends to confuse both implementors and content authors. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/218#issuecomment-370787038
Received on Tuesday, 6 March 2018 13:51:29 UTC