Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

epub:type restricted to palpable content may cause backward incompatibilities #2486

Closed
rdeltour opened this issue Nov 29, 2022 · 1 comment · Fixed by #2493
Closed

epub:type restricted to palpable content may cause backward incompatibilities #2486

rdeltour opened this issue Nov 29, 2022 · 1 comment · Fixed by #2493
Labels
EPUB33 Issues addressed in the EPUB 3.3 revision Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Topic-Vocab-Association The issue affects the vocabulary association mechanisms

Comments

@rdeltour
Copy link
Member

In EPUB 3.3, XHTML requirements says the epub:type attribute MUST only be used on palpable content.

This list is restrictive and will likely cause a lot of existing material being rejected. Several HTML elements like body or li are not palpable content but are often associated an epub:type attribute (they're defined as relevant usage context in the structural semantics vocabulary).

Also, it means epub:type and hidden cannot co-exist, I'm not sure how that's relevant.

Was the idea was to not allow epub:type on some elements like head and style?

If yes, we could either:

@mattgarrish mattgarrish added Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Topic-Vocab-Association The issue affects the vocabulary association mechanisms labels Nov 29, 2022
@mattgarrish
Copy link
Member

mattgarrish commented Nov 29, 2022

epub:type is not supposed to be used on the head element or within it as the header doesn't contain structural content.

The restriction was previously only on reading systems to ignore the attribute in the head element, but an authoring restriction was added to match. Agree that palpable doesn't look right.

I'm fine switching it to "MUST NOT be used on the head element or on metadata content". This would also capture uses on script, link, etc. in the body, as these are not structural elements in the sense that the attribute was created for.

@mattgarrish mattgarrish added the EPUB33 Issues addressed in the EPUB 3.3 revision label Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPUB33 Issues addressed in the EPUB 3.3 revision Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Topic-Vocab-Association The issue affects the vocabulary association mechanisms
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants