xz / xz/new.css

Add `ui-monospace` to the `--nc-font-mono` stack

Open
#86 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
4.1k
Forks
127
PR merge metrics
No merged PRs in 30d

Description

Making an Issue first since I'd like to bikeshed gather opinions on where in the stack to put it.

As of this writing, the --nc-font-mono stack is this:

--nc-font-mono: Consolas, monaco, 'Ubuntu Mono', 'Liberation Mono', 'Courier New', Courier, monospace;

I tried viewing this on my iPad, and I got Courier (New?). Since the rest of new.css uses nice, modern sans-serif fonts, it stuck out like a sore thumb.

Happily, changing the font stack to

    --nc-font-mono: ui-monospace, Consolas, Monaco, "Ubuntu Mono",  "Liberation Mono", "Courier New", Courier, monospace;

made it so I got .AppleSystemUIFontMonospaced (SF Mono). This looks way better on my iPad.

I suggest putting ui-monospace right before Monaco, so the line reads:

	--nc-font-mono: Consolas, ui-monospace, Monaco, 'Ubuntu Mono', 'Liberation Mono', 'Courier New', Courier, monospace;

My rationale:

  1. Monaco is a Mac OS/OS X/macOS-only font.
  2. Monaco has only one weight and one style: Normal. No bold, no italic, no bold italic. As much as I like Monaco as a typeface, it's not a good font.
  3. The last version of Safari to support only Monaco and not ui-monospace was superseded in March of 2020.
  4. Chrome and Firefox on macOS will still pick up Monaco, which is still better than any Courier font in most cases.

Thoughts?

(Also, I'd properly capitalize Monaco in passing, but that's much less important.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the project for the --nc-font-mono definition and inspect its current font stack. Add ui-monospace in the proposed position, capitalize Monaco consistently if appropriate, and verify that the resulting CSS variable matches the issue's requested stack.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.