Skip to content

Idea for improving the font selector #379

Open
@StealthWombat

Description

@StealthWombat

Font selectors in editors are all very well, but invariably they come pre-stocked with a few old Windows fonts and nothing else. This means that if the person viewing your post doesn't have the same font installed, they won't see what you intended them to see.

Standard web practice when writing CSS is to use font stacks rather than single fonts, so you get a reasonably consistent look on any platform. It's easy to find a pile of pre-generated font stacks for just about any primary font, with suitable fallbacks as far as you like.

So, offhand I'm thinking it would make sense to pre-stock the editor options with decent stacks. The problem is that with all the single font options already done as a comma-separated list, it doesn't seem feasible to change each single option to a stack (which obviously would have to be a comma-separated list itself).

Any thoughts about this?

Cheers.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions