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
when including part of the boostrap css in an epub V3 file as epubcheck is reporting an error on empty value for custom css properties. After verification I agree with the boostrap team that it is legal CSS for custom properties to be empty whereas it is not legal for regular properties to be empty and it seems it is a bug in epubcheck to report this as an error.
To replicate the error simply take the boostrap CSS here
and include it in an epub3 file, then run epubcheck vs 5.0.1 and you will get an error like this:
ERROR(CSS-008): ../untitled.epub/OEBPS/Styles/main.css(2731,25): An error occurred while parsing the CSS: Token ";" not allowed here, expecting a property value.
The text was updated successfully, but these errors were encountered:
I agree this looks like a bug, good catch! If I remember correctly, EPUBCheck's custom CSS parser was implemented even before CSS custom properties were a thing. I'll look into it for the next milestone.
Hello I'm also running with an issue similar to the one describe here
twbs/bootstrap#38061
when including part of the boostrap css in an epub V3 file as epubcheck is reporting an error on empty value for custom css properties. After verification I agree with the boostrap team that it is legal CSS for custom properties to be empty whereas it is not legal for regular properties to be empty and it seems it is a bug in epubcheck to report this as an error.
To replicate the error simply take the boostrap CSS here
https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.css
and include it in an epub3 file, then run epubcheck vs 5.0.1 and you will get an error like this:
ERROR(CSS-008): ../untitled.epub/OEBPS/Styles/main.css(2731,25): An error occurred while parsing the CSS: Token ";" not allowed here, expecting a property value.
The text was updated successfully, but these errors were encountered: