User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/103u (KHTML, like Gecko) Safari/100 Build Identifier: 20031029 (Mozilla 1.6a) Integrate with the Mac OS X 10.3 Font Book program so that user-specified font collections can be accessed and used from within Mozilla. Reproducible: Always Steps to Reproduce: 1. 2. 3.
How would you suggest this be intergrated? I don't even Safari does this... do you mean to have Mozilla render what your font selection looks like in real time... similar to the font set up in Camino or Safari?
Integration would be with HTML mail compose and Composer. It would allow windows to be drawn faster by reducing the number of fonts in the font selection list.
How would using FontBook allow faster window drawing? Sorry for such a simple question but I just don't follow Font Book that much as I am not that interested in Font management... Reading Apples Font Book page [http://www.apple.com/macosx/features/fontbook/], to me it seems as if one would be able to better maniplate fonts styles when composing email and what not... but the major question is this... will the kerning, letteer spacing, height, and everything else get passed along in the email... html email... does a CSS porperty exist for some of the things Font Book allows the user to do? It would be cool and all... just wondering.
Not sure how well styling would transfer. This might not be a valid bug after all now that I look more at Font Book. Reducing the number of fonts does speed up compose window drawing as the font list is shorter.
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420