User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030522 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030522 Mozilla Firebird/0.6 Firebird displays only fonts that match (?) to encoding or something in the font listing combo boxes. For example, in "Western", the listing in Serif box in Mozilla suite Preferences is like: ################################################# [System Default] ------------------------------- (separator line) Century CenturyOld Georgia . . . Times New Roman -------------------------------- (another separator) %Century Oldst Arial . . . ############################################### and you can set fonts under the second separator, but in Firebird, it simply omits listing of all the fonts under the second separator and the line "[System Defaults]" Reproducible: Always Steps to Reproduce: Expected Results: Firebird should list all fonts ala Mozilla.

From what I can determine, this is behaviour by design. The font lists are based on category, so monospace fonts can't be selected for proportional and vice versa. If you really want to pick a specific font you can probably do it via about:config to override, but the UI is designed to be simple and user-friendly. The average user won't know what monospace vs. proportional is, so Firebird is correctly limiting the choices to appropriate fonts. --> WONTFIX

See comment above, marking WONTFIX. Removing dependency, since that bug won't allow non-matched to encoding fonts, it'll just improve support for other character sets etc.

The behaiver in mozilla was changed, when it was discovered that it leads to very bad bugs like bug #110655. (see also bug #142511 comment #19). Are we sure that we are able to prevent such problems?

BTW, for the same reason, bug #206780 is still broken for Hebrew on OSX, just like the original Mozilla bug broke it. If this is anything like in Mozilla, that bug won't be fixed until this bug is. Therefore, I am reopening this one.

taking QA contact, sorry about the bugspam

How could you possibly tell whether a bug is not fixed on a build four days older than the checkin for the bug in question? Regardless, having read bug 110655 I suspect it probably won't. However, just because Seamonkey fixed this with a fat and bloated fonts box doesn't mean we will do the same for Firebird just to fix Hebrew on OS X. I appreciate that its important to you, but there needs to be a better fix than simply show all fonts. See the comments in bug 142511 comment 31 regarding the visible perf hit this change represents. Returning this to WONTFIX. Once a Mac OS X build appears with the fix in place, if it still doesn't work, please file a new bug against Firebird on that specific issue, mentioning the two bugs you mentioned here. We could always reimplement the bloated fonts box on OS X only, but for non-Mac, non-Hebrew reading, the perf regression is far too large. Out of curiousity, how does Camino handle this?

>Out of curiousity, how does Camino handle this? It is completely broken there, as the user has no way to control the font for Hebrew display, and many times you get incorrect display, with no way to fix it. Since Apple Safari came out, many users have been switching over, althugh it has it's own share of bidi bugs, at least you can control what font it uses. >Once a Mac OS X build appears with the fix in place Any idea when that will be? MFB is not really usable with that bug in place.

Forgot to mention- I talked to Camino's Devs, and they will handle it the same way Mozilla does, once they re-sync to the trunk.

Well, aside from Hebrew on Mac OS X, in original bug I'm talking about Japanese on Windows XP. I doubt Firebird can inteligently choose appropriate fonts. For the specific point I'm annoyed I can't choose the same font in Serif and Sans-serif because original inteligent version of Firebird doesn't show proportinal fonts in San-serif. OK the average user doesn't need it, then for more generic point, Monospace box was just too broken to display Japanese correctly, limiting fonts inappropriately. I'm not sure what's going on currently but as in Bug 206780 comment #19 it's been set back to Mozilla style, so I don't reopen this bug for now.

VERIFYING obvious WONTFIX bugs. Filter on firebirdWontFix to filter these bugs. I skipped a few that I'm unsure about from their summary and will manually go through them.

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change