Support for CSS2 system fonts would be nice. These allow fonts from the user's UI to be specified. See also bug 1004, relating to system colors.

In bug 1004, sfraser@netscape.com write: > The list of font values in the spec is rather restrictive; controlling fonts > in various places in the UI will probably require a few more values. > > All the dialog work is dependent on this, in the sense that dialog layout > cannot be finalized until we can display the correct fonts. I would thus > hope that this could be moved to M5 or M6 if possible. Setting severity/priority to enhancement/P1. This is an RFE but is required for the UI stuff.

Testcase for this: http://www.fas.harvard.edu/~dbaron/css/test/sec1803

Moving non-beta 1 items to M15

Reassigning peterl's bugs to myself.

Accepting peterl's bugs that have a Target Milestone

More work needs to be done in MapDeclarationFontInto(). The nsCSSFont.mFamily is correctly set (look for NS_STYLE_FONT_CAPTION ... NS_STYLE_FONT_STATUS_BAR in nsStyleConst.h) but not the nsStyleFont->mFont.name.

Note that CSS3's UI >>draft<< spec introduces a lot of new fonts as well, namlely: window | document | workspace | desktop | info | dialog | button | pull-down-menu | list | field See http://www.w3.org/TR/css3-userint for the latest draft.

Pushing my M15 bugs to M16

Migrating from {css2} to css2 keyword. The {css1}, {css2}, {css3} and {css-moz} radars should now be considered deprecated in favour of keywords. I am *really* sorry about the spam...

It's fixed in XP code and on the Mac. I opened separate bug reports for Windows (bug 33312) and Unix (bug 33313). The dependencies will be updated.

Netscape's standard compliance QA team reorganised itself once again, so taking remaining non-tables style bugs. Sorry about the spam. I tried to get this done directly at the database level, but apparently that is "not easy because of the shadow db", "plus it screws up the audit trail", so no can do...

verified (on Mac) that we do something for each of the fonts.