I think these rules may be sufficiently specific that they will override the <style> tags we insert into the body to implement Settings → Display Preferences → Monospaced Font:

• If you set that to something like 24px "Impact", is your preference still respected?

hmmm no... i think i'd have to make the ones in head more specific?

I don't think it's necessarily bad to say that the preference doesn't count on Phriction pages, but if we go that way we should make it fully not count instead of counting the font family but not the font size.

Let me think about this. Also, I have 'Source Code Pro' from Adobe (free) in a branch in my sandbox. It'd be interesting to offer some monospace options via a dropdown and bundled vs. making each developer individually install them. Monospace still looks like crap on Windows/Linux. http://blog.typekit.com/2012/09/24/source-code-pro/

I wonder if user inputed should just include !important. I know you hate that, haha.

I think it's 100% fine in this case.

Doesn't work then. Looks like we set Monospace in the head regardless of if it's default or custom.

Where does the "Global Default" get set in the code? I've grepped around and can't find a source. Ideally, I want to make the global default null and have it CSS driven. Then if install admins or users pick something else, push that up with !important.

I guess its driven right from PhabricatorSyntaxHighlightingConfigOptions ? Will poke there.

You can grep for, e.g., Monaco to find where the global default is. Looks like PhabricatorSyntaxHighlightingConfigOptions.

yup

Yeah, that blew my mind it, I assumed that to be an example, not the actual default.