search

w3c / wpub

W3C Web Publications
https://w3c.github.io/wpub/
Other
79 stars 19 forks source link

Optional HTML TOC #402

Closed geoffjukes closed 5 years ago

geoffjukes commented 5 years ago

If the HTML TOC is defined in the manifest, is there any facility for making its use optional? Or does its presence imply it must be used?

I can imagine early adopters generating crude TOCs, but not actually caring if they are used.

iherman commented 5 years ago

We have not defined, and I am not sure we should, the exact user agent behaviour. That also means that the data is there but the user agent chooses to ignore it, that is fine.

llemeurfr commented 5 years ago

@geoffjukes to be precise, the HTML ToC will be referenced from the manifest, not "defined in". It will be represented as a standard HTML resource and this resource will be optional. In the absence of this resource, the user agent (the player) will be able to use the reading order (track listing) as a fallback (this is the current practice).

I believe that we should describe user agent intended behavior in a best practice document at least.

iherman commented 5 years ago

I believe that we should describe user agent intended behavior in a best practice document at least.

I agree

iherman commented 5 years ago

This issue was discussed in a meeting.