Font Name in Editor doesn't show state for Arial, others not on list

[peller]

This appears to be a shortcoming of FilteredSelect. How do we get it to show values not on the list?

[peller]

As Bill points out, there are a large number of issues with editor fonts, portability across locales and operating systems, and even with importing content, but to list them here would likely confuse a number of bugs.

The bug is simply that selecting a range in IE results in a font of Arial which is not presently on the list. A kludge would be to add that one font to the list. A more general solution would be to allow for any selected font to be tolerated by the Font Name toolbar widget, even if it's not in its known list.

To reproduce, in IE:

load test_Editor.html
look for editor with font name dropdown
select a range and select a font.
click on something else
the selection comes back as arial and the filtered select shows a warning and an inconsistent state with the last font chosen

it may be more involved than this, as I haven't investigated fully. I wanted to jot something down so this wouldn't get lost.

[bill]

mapping code for serif --> arial, etc _{plus an abbreviated test file with sample text in each font.}

[peller]

(In [12964]) Nedes more testing. Let's play with this set up. Allows custom fonts on djConfig to replace CSS "generics", and maps them back so IE is sane. Refs #6029 !strict

[peller]

(In [12983]) A bit more hacking on fonts. Quote fonts with space on safari and process single quotes. Refs #6029

[peller]

(In [13060]) Add font examples in content, remove bogus fontName definition. Fixes #6179 Refs #6029

[peller]

(In [13061]) specify generics, custom list as options on FontChoice. Fixes #6029, #6035

[peller]

hmm... just realized there is another aspect to this. I think what I originally meant was the ability to have FilteringSelect pick up values on-the-fly, whether based on selection or by the user typing something into the field that isn't in the data store. The mapping we put in place only solves the problem wrt CSS generic fonts, but there are endless font choices out there. Think about this for 1.2+

[bill]

Unlikely this will be fixed unless someone wants to supply a patch (including a test case).