| Summary: | CSS: Request for proprietary extension to generic font families 1: 'monospace' | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Nicholas Shanks <nickshanks> |
| Component: | CSS | Assignee: | Nicholas Shanks <nickshanks> |
| Status: | RESOLVED INVALID | ||
| Severity: | Enhancement | CC: | ap, bfulgham, mmaxfield |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
This idea should be discussed in the relevant CSS working group. Right, Brent is right. The correct place to request this feature is at https://github.com/w3c/csswg-drafts/issues/new |
I would like the 'monospace' generic family to be seen as orthogonal to 'serif' and 'sans-serif' in the generic font-family fallback keywords. I envisage sites using it in this way: code { font-family: "Consolas", monospace serif, monospace; } Where WebKit would recognise monospace serif as meaning 'use Courier, not Monaco'. Other browsers would look for a font called 'monospace serif', not find one, and fall back to the generic of monospace. WebKit would ned to be hard‐coded with lists of Monospace fonts (which I believe it already has) but divided up into serif and sans‐serif.