View Single Post
Old 06-22-2020, 10:52 AM   #2235
jgoguen
Generally Awesome Person
jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.
 
Posts: 1,100
Karma: 2191133
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
Quote:
Originally Posted by davidfor View Post
But, even with that class defined, aren't all the styles just going to pass through it?
After some digging, it seems "-webkit-text-combine" has only two values (other than the implicit "inherit" available on all inheritable properties): "horizontal" and "none". "none" is the default, "horizontal" is the same as the standard CSS property "text-combine-upright: all" (which is currently the only valid value other than "none" according to the standard; CSS4 includes a "digits" keyword that makes it apply only to digits, e.g. "digits 2" and "digits" are the same, "digits 4" applies to up to 4 consecutive digits).

According to the "text-combine-upright" standard, this breaks across box boundaries; "<p>This is text</p>" could have it applied, but "<p>This is <span>text</span> in a box</p>" would break and user agents should treat it as though "text-combine-upright" were set to "none". That doesn't seem to be always true in practice, at least Chrome attempts to do the intuitive thing and effectively sets the default values as "-webkit-text-combine: inherit" and "text-combine-upright: inherit". Kobo's style declaration seems to be either saying the ACCESS renderer adheres to the standard or is acknowledging that books may be read on devices which do.

So yes, in theory this should be a no-op for most books. But it does have me wondering if I should be trying to make sure that style declaration is present.
jgoguen is offline   Reply With Quote