-
Notifications
You must be signed in to change notification settings - Fork 407
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
"rel" attribute disallowed in "a" element inside "svg" element (epubcheck 4.2.2) #1172
Comments
Yes, it's valid, but the schemas don't fully support svg2. I've opened an issue against the nu validator to add: validator/validator#1008 |
I am not an svg expert, but I am concerned that it will be difficult to validate svg in the era of living standards. An svg 1.1 validator should reject the example since |
That's what I understand is done for the nu validator based on this discussion I found. For epubcheck, my understanding is that we want to be in sync with web validation generally, except where epub specifically diverges, so that you don't get mixed signals. That isn't entirely possible at this stage, since we only use the schemas and not the additional java checks, but I believe fuller integration might come in a later refactor of epubcheck. No opinion here on whether or not to check svg, though. That would be a discussion for the main group to pick up. |
Note that I updated the initial description of this bug to remove |
Another example of a similar issue is this error:
when presented with:
|
I think that SVG validation should not be lifted, since maintenance of EPUB assets containing invalid SVG fragments is likely to be annoying. |
While I'm fine if the EPUB specs ultimately do not require validity for conformance, it would greatly reduce the usefulness of epubcheck if we stop checking the validity of SVG and XHTML files completely. Perhaps we need to consider other options, like defining a separate message category for validity issues or only strictly validating if a flag is set. |
SVG content model checks are now informative only since #1365. |
The nesting in the title yields the following error:
An extract of markup would be (ellipses indicate clipped markup):
I think this should be okay. Does the SVG schema need updating?
The text was updated successfully, but these errors were encountered: