View Single Post
Old 12-19-2014, 02:11 PM   #144
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by shamanNS View Post
@dgatwood: I was speaking primarily about CSS & ebooks that are targeting Kindle devices. Also, it is matter of proper implementation of html and CSS, and there it shouldn't be a choice if by default child tag inherits from parent. CSS specification says that font-family is inherited. And body tag is top most parent.
It has nothing to do with the spec's inheritance behavior; if the reader's stylesheet has:

PHP Code:
h1 font-family: ... ; } 
then setting the font on the body won't do the trick. I don't entirely trust them not to set default heading fonts that are different from the body font in the future. After all, if it makes sense for book authors to do so...
dgatwood is offline   Reply With Quote