KEMBAR78
Explain legacy elements · Issue #2423 · w3c/epub-specs · GitHub
Skip to content

Explain legacy elements #2423

@mattgarrish

Description

@mattgarrish

There still seems to be confusion about the purpose of the legacy elements. They exist only for allowing EPUB 3s to render, as much as possible, in EPUB 2 reading systems.

The spec doesn't introduce this purpose in the package document's legacy content section, so it requires users to follow the link on the word legacy in almost all cases to get to the definition (oddly, we explain the purpose for the meta element in a note).

I wonder if we should even bother having legacy elements described in the unsupported features section, since they only apply to those elements (plus the toc attribute for referencing the NCX). It would be clearer to move the prose up to the section.

Metadata

Metadata

Assignees

No one assigned

    Labels

    EPUB33Issues fixed in the EPUB 3.3 revisionSpec-EPUB3The issue affects the core EPUB 3.X Recommendation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions