You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
What is "XHTML content document Phrasing content"? #2355
The link just redirects back to the general xhtml requirements, however; there are no references to phrasing content.
I assume this is supposed to mean HTML phrasing content that conforms to the XHTML content document restrictions, but it's not clear at all from the description.
It also makes it sound like you have to have an xhtml namespaced element even if the title is text only. I know the phrasing content definition includes text, but the description makes it sound like all content needs to be in the xhtml namespace.
Although, going back to the SVG spec definition, this is kind of a weird restriction. According to SVG2:
The display value for the ‘title’ and ‘desc’ elements must always be set to none by the user agent style sheet, and this declaration must have importance over any other CSS rule or presentation attribute.
So titles are never displayed by default, and the definition says the element is never-rendered content. The spec goes on to reinforce this:
Description and title elements may contain marked-up text from other namespaces, using standard XML mechanisms to indicate the namespace. However, authors should not rely on such markup to provide meaning to alternative text; only the plain text content is currently required to be exposed to assistive technologies.
The only purpose of markup in a title appears to be optional and probably not supported:
User agents may use markup within ‘title’ to influence the visual presentation of titles (such as tooltips), but are not required to do so.
So the restriction is just in case a reading system wants to style a tool tip? Meanwhile we allow foreign elements everywhere else?
I just checked epubcheck and it doesn't enforce this restriction. You can put any elements in the title.
Activity
mattgarrish commentedon Jul 12, 2022
Although, going back to the SVG spec definition, this is kind of a weird restriction. According to SVG2:
So titles are never displayed by default, and the definition says the element is never-rendered content. The spec goes on to reinforce this:
The only purpose of markup in a
titleappears to be optional and probably not supported:So the restriction is just in case a reading system wants to style a tool tip? Meanwhile we allow foreign elements everywhere else?
I just checked epubcheck and it doesn't enforce this restriction. You can put any elements in the title.