Quote:
Originally Posted by Falkor
Why are you making such a big deal out of this? It's CSS. It evolves. Prefixed properties are not uncommon. They won't break anything, because CSS is forward compatible. Unsupported properties will be ignored. If different renderers use different properties to achieve the same thing, you will have to use more than one to maximize compatibility.
We're supposed to jump through hoops to ensure backwards compatibility with RMSDK’s broken error parsing–which certainly isn’t ePub2 compliant–but prefixed properties are supposed to be a problem?
Also, ADE 4.5 does support several webkit-prefixed properties. I have successfully used -webkit-column-break-after for page breaks and -webkit-initial-letter for drop caps. The standard "initial-letter" is not supported.
|
Because it's spreading incorrect information.
There is a way around the older RMSDK's CSS bug. Use @support for any CSS that causes RMSDK to ignore the CSS. The other issue is that there are a lot of Readers out there in use that use an older RMSDK that does not support webkit. For example, Kobo uses some version 3 RMSDK and they are current Readers that are used by a lot of people. Some still use a Sony Reader which uses an even older RMSDK.