| Positives | Negatives |
|---|---|
| Great browser support | _ |
| Easy for end users to implement | _ |
| Small file size | _ |
| _ | No context if they fail to load... |
| _ | ...Or user overrides fonts^1 |
| _ | Rendering inconsistent between systems (antialiasing) |
| _ | Not supported in Opera Mini |
| Positives | Negatives |
|---|---|
| No conflict with fonts | _ |
| Consistent rendering between systems | _ |
| Fixed colours and sizes* | Fixed colours and sizes* |
| _ | No context if they fail to load^2 |
| _ | Larger filesize, slower to render than a webfont |
| _ | Slightly more complex for end users to implement |
| _ | Advantages of SVG lost by need for fallback^3 |
* With a design leadership hat on this is a positive IMO
- Potentially solved by using ligatures but that drops support for <= IE9 (text-only fallback)
- Could be solved by forcing end-users to implement text by displaying an error with
:emptypseudo-selector - Could supply text-only fallback to non-SVG capable browsers (IE8, Android 2.x)
Anything I've missed?
