Technically, HTML fragment indication and scrolling is defined only for HTML documents. However, in practice, browsers use it for other types as well. Safari invokes text directives for multiple text-based media types while Chrome restricts itself to text/html and text/plain, avoiding other types for security reasons (see
https://crbug.com/1270469).
Make this explicit in the spec, though perhaps this should be made explicit elsewhere (e.g. RFC
5147 defines fragment identifiers for text/plain).
Technically, HTML fragment indication and scrolling is defined only for HTML documents. However, in practice, browsers use it for other types as well. Safari invokes text directives for multiple text-based media types while Chrome restricts itself to text/html and text/plain, avoiding other types for security reasons (see https://crbug.com/1270469).
Make this explicit in the spec, though perhaps this should be made explicit elsewhere (e.g. RFC 5147 defines fragment identifiers for text/plain).
Preview | Diff