View Single Post
Old 10-03-2014, 02:59 PM   #87
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,049
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by dgatwood View Post
On readers that handle fonts correctly, the entire "hidden" span collapses into a zero-width inline element. On readers that abusively override the font selection, it shows up as red text in the reader's default paragraph font.

Note that this approach is entirely compatible with well-behaved readers that change only the body tag's font, because a reader stylesheet that overrides the font on the body tag (and only the body tag) won't cause that hidden text to appear. However, if you really need to force the body text to a particular font, declare a paragraph style with a font choice and !important. Then, odds are good that any reader that overrides the paragraph font will also get tripped up by the canary above, and any reader that doesn't won't be.
I just tried this using Bluefire Reader and it didn't work. I overrode the default embedded font and I did not see BlankFont show up in red at all.
JSWolf is offline   Reply With Quote