View Single Post
Old 11-02-2011, 08:55 PM   #6
Jim Lester
Evangelist
Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.Jim Lester is less competitive than you.
 
Jim Lester's Avatar
 
Posts: 416
Karma: 14682
Join Date: May 2008
Location: SF Bay Area
Device: Nook HD, Nook for Windows 8
It's not your @font-face rules, it's the font-family attribute in subsequent rules in your OPF.

For instance, if you had

body {
font-family: "Times"
....
}

This would get nicely overridden by the user style sheet to be what the user actually selected.

If however you had

p.myclassid {
font-family: "Times"
}

This isn't currently being overridden by the user style sheet. The result at worse is a ransom note effect with the fonts being a mix of the author (your) selected fonts, and the user selected fonts.

Putting the font-family attribute in the least specific selector (such as p, div, or body) that you can get away will potentially avoid this.
Jim Lester is offline   Reply With Quote