View Single Post
Old Yesterday, 02:59 PM   #61
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,447
Karma: 20456789
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by jhowell View Post
While I agree with your stance on property names that begin with "-webkit-" and other prefixes, if you look at the cited appendix it becomes clear that "Prefixed properties" in this case refers to property names that begin with the "-epub-" prefix.
I noted that as well. However, the spec is talking about ePub so it would make sense to only demo -epub- prefixes. In the real world the devices/apps DO support prefixes of all types to some degree or another. The argument was being made that using prefixes wasn't allowed...that is not true.

Best practice would be to use the non-prefix if it's supported, prefixed if necessary. Either way is legal and epubcheck doesn't give a fit over their use.

To Jon's latest goal post movement - ignoring an unsupported style is exactly what epub is supposed to do. That is not broken. That is what coder's rely on when they create epubs that are backwards compatible...it's all part of the fallback coding concept.

Last edited by Turtle91; Yesterday at 03:01 PM.
Turtle91 is offline   Reply With Quote