Closed Bug 410575 Opened 17 years ago Closed 17 years ago

I don't care about default Cursive or Fantasy fonts, and I bet you don't, either

Categories

(Camino Graveyard :: Preferences, defect)

1.8 Branch
All
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Camino1.6

People

(Reporter: mark, Assigned: mark)

Details

(Keywords: fixed1.8.1.12)

Attachments

(3 files, 3 obsolete files)

In Camino:Preferences:Appearance:Fonts:Advanced…, we let users set default fonts for Cursive and Fantasy styles.  These were lightly used even when these generic family names were first introduced, and I think their use has only diminished with time.  I can't imagine any site actually specifies cursive or fantasy without reasonable fallbacks, and in any case, these guys can remain editable as hidden preferences.

I propose we eliminate the UI to set default faces for the cursive and fantasy generic families.

If we do this, we can probably get rid of the Advanced sheet altogether, although we can discuss that further or do the work in another bug.
The fox had eliminated those a long time ago, actually...
(and as a page author, I do care about them, once every 2 years or so :-))

For the reworking of the font prefs, is bug 184102 still something to keep an eye on ? That is already much less complex than the current implementation.
I'm all for it (especially in conjunction with removing "advanced" through something like the mocks in 184102, but without is fine too).
The main problem with getting rid of Advanced is that it is the only way (on branch) we can set fonts correctly for Asian languages (on trunk, we have no such way, because they're using yet another API for enumerating and assigning font names :/ ).

I'd really like to do away with Advanced altogether (if we can keep the new UI the height of the existing pane, because we can't make Colors & Links any bigger without the content getting lost in the empty room), but we can't yet.  Having two UIs to do the same thing is also stupid, of course, but the "enormous scolling font list UI" really sucks....
Attached patch v1, remove Cursive and Fantasy (obsolete) — Splinter Review
This removes the UI for setting Cursive and Fantasy fonts.  But we probably want to add monospaced fonts to the advanced sheet for the CJK reasons Smokey gave above.
Assignee: nobody → mark
Status: NEW → ASSIGNED
Attached file v1 nib (obsolete) —
Attachment #295267 - Attachment is obsolete: true
Attachment #295286 - Flags: review?(stuart.morgan)
Attached file v2 nib
Attachment #295269 - Attachment is obsolete: true
Attachment #295289 - Flags: review?(alqahira)
(See also bug 410733; there are other fonts out there that return different names to different APIs.  Suck.)
Comment on attachment 295286 [details] [diff] [review]
v2, remove Cursive and Fantasy, add Monospace to the Advanced sheet (trunk)

r=me

>-          monospace =   {
>-              fontfamily =
>-            }

Shouldn't this still be here, since it is one of the things added to the dict? Obviously not critical; just wondering why you are removing it.
Attachment #295286 - Flags: review?(stuart.morgan) → review+
In haste, I bet I figured that whatever came after cursive had to be fantasy.  I'll leave it in when I check this in.
Comment on attachment 295288 [details] [diff] [review]
v2, remove Cursive and Fantasy, add Monospace to the Advanced sheet (1.6)

Erm, FWIW, this is the trunk patch again (which has a minor context conflict with our work-around-Carbon-suck stiff in Appearance.h).
Comment on attachment 295289 [details]
v2 nib

r=ardissone
Attachment #295289 - Flags: review?(alqahira) → review+
Branch patch for real.
Attachment #295288 - Attachment is obsolete: true
Comment on attachment 295583 [details] [diff] [review]
v2, remove Cursive and Fantasy, add Monospace to the Advanced sheet (1.6)

When I apply this, shared works OK, but static doesn't pick up the Monospaced menu (i.e., it's got dummy items in it, instead of a list of fonts) and I can't close the sheet (or prefs, etc.) without  Force Quitting.
2008-01-06 22:42:17.792 Camino[515] *** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value

is what I see in the Console when running static (i386, PPC under Rosetta, PPC 10.3.9)
It sounded like the new nib got mixed up with the old code - Smokey took another look and the problem vanished for him.
Checked in on the trunk and MOZILLA_1_8_BRANCH before 1.6b1.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Keywords: fixed1.8.1.12
Resolution: --- → FIXED
Target Milestone: --- → Camino1.6
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: