Closed
Bug 198546
Opened 22 years ago
Closed 22 years ago
Format -> Font submenu doesn't deal with "unknown" font
Categories
(SeaMonkey :: Composer, defect)
SeaMonkey
Composer
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jag+mozilla, Assigned: jag+mozilla)
References
Details
(Whiteboard: [adt2])
Attachments
(3 files, 4 obsolete files)
2.36 KB,
patch
|
glazou
:
review+
|
Details | Diff | Splinter Review |
6.70 KB,
patch
|
Details | Diff | Splinter Review | |
4.19 KB,
patch
|
jag+mozilla
:
review+
bryner
:
superreview+
|
Details | Diff | Splinter Review |
If the selection has a font applied that we don't know about (isn't one of the
three we assume or isn't one of the system fonts) we end up selecting "variable
width" instead of selecting nothing.
Comment 1•22 years ago
|
||
-->jag
jag--you should use cmd_fontFace and query it for the font (if this is what this
bug is about)
Assignee: composer → jaggernaut
Keywords: nsbeta1
Comment 2•22 years ago
|
||
Composer triage: nsbeta1+/adt2
Assignee | ||
Comment 3•22 years ago
|
||
Comment 4•22 years ago
|
||
Comment on attachment 120198 [details] [diff] [review]
Rewrite font submenu font selection code to be faster and to deal better with unknown fonts
you can use command api like this:
var cmdParams = newCommandParams();
goDoCommandParams( "cmd_fontFace",cmdParams);
fontFaceStr = params.getCStringValue("actualFont")
fontMenuState = params.getCStringValue("state_attribute");
...
Comment on attachment 120198 [details] [diff] [review]
Rewrite font submenu font selection code to be faster and to deal better with unknown fonts
r=glazman
Attachment #120198 -
Flags: review+
Assignee | ||
Comment 6•22 years ago
|
||
See bug 201650.
Assignee | ||
Comment 7•22 years ago
|
||
Attachment #120198 -
Attachment is obsolete: true
Assignee | ||
Comment 8•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Attachment #120682 -
Attachment is obsolete: true
Assignee | ||
Comment 9•22 years ago
|
||
Comment on attachment 120684 [details] [diff] [review]
And make sure we still correctly claim no font face applies.
r=glazman
Attachment #120684 -
Flags: review+
Assignee | ||
Comment 11•22 years ago
|
||
Since the previous JS patch somehow confuses the Mac menu code, falling back to
the old code, but doing a quick check to see if the default font applies. If
not, assume it's mixed or unknow and select nothing.
Assignee | ||
Comment 12•22 years ago
|
||
Attachment #120695 -
Attachment is obsolete: true
Assignee | ||
Comment 13•22 years ago
|
||
Since for some unknown reason the JS in attachment 120686 [details] [diff] [review] screws up on Mac,
I've gone back to the old (and less efficient) JS, but with a fix for this bug
(namely not selecting anything instead of "variable width" for unknown fonts.
Attachment #120699 -
Attachment is obsolete: true
Assignee | ||
Comment 14•22 years ago
|
||
Comment on attachment 120704 [details] [diff] [review]
Optimization pointed out by Neil
Neil said r=Neil
Attachment #120704 -
Flags: superreview?(bryner)
Attachment #120704 -
Flags: review+
Updated•22 years ago
|
Attachment #120704 -
Flags: superreview?(bryner) → superreview+
Assignee | ||
Comment 15•22 years ago
|
||
Checked in. Filed bug 202385 to deal with making this code use cmd_fontFace.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 16•22 years ago
|
||
do we need to make a similar fix in the compose window, where shuehan recently
added a font picker?
Comment 17•22 years ago
|
||
What's the best way of verifying this bug ?
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•