Bug 17069 - CSS: Request for proprietary extension to generic font families 1: 'monospace'
Summary: CSS: Request for proprietary extension to generic font families 1: 'monospace'
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Enhancement
Assignee: Nicholas Shanks
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-29 13:29 PST by Nicholas Shanks
Modified: 2022-07-16 19:50 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicholas Shanks 2008-01-29 13:29:54 PST 
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.
Comment 1 Brent Fulgham 2022-07-11 16:10:18 PDT 
This idea should be discussed in the relevant CSS working group.
Comment 2 Myles C. Maxfield 2022-07-16 19:50:15 PDT 
Right, Brent is right. The correct place to request this feature is at https://github.com/w3c/csswg-drafts/issues/new