Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Monospace font not being chosen correctly when font-family starts with missing fonts

more options

I've just started noticing in Firefox 99 on Arch Linux that Firefox is using the wrong font when the font-family is given as "ui-monospace/other fonts..., monospace". This looks similar to the issue mentioned here: https://support.mozilla.org/en-US/questions/1351497

The inspector for these websites underlines "monospace" as the active font, but then uses a non-monospace font (in my case, Bitstream Vera Sans) to display the content. This does not happen when the font-family is "monospace,monospace" or "monospace". I can't quite figure out exactly what causes the font to be chosen incorrectly: sometimes it does show up if I have the preceding fonts installed, e.g. Consolas or Liberation Mono, but other instances do not look as intended.

Currently, I have fontconfig set up such that: $ fc-match :family=ui-monospace VeraMono.ttf: "Bitstream Vera Sans Mono" "Roman" $ fc-match :family=monospace VeraMono.ttf: "Bitstream Vera Sans Mono" "Roman"

Firefox's fonts in about:preferences are configured as all defaults: Serif: Bitstream Vera Serif Sans: Bitstream Vera Sans Monospace: Bitstream Vera Sans Mono

I've just started noticing in Firefox 99 on Arch Linux that Firefox is using the wrong font when the font-family is given as "ui-monospace/other fonts..., monospace". This looks similar to the issue mentioned here: https://support.mozilla.org/en-US/questions/1351497 The inspector for these websites underlines "monospace" as the active font, but then uses a non-monospace font (in my case, Bitstream Vera Sans) to display the content. This does not happen when the font-family is "monospace,monospace" or "monospace". I can't quite figure out exactly what causes the font to be chosen incorrectly: sometimes it does show up if I have the preceding fonts installed, e.g. Consolas or Liberation Mono, but other instances do not look as intended. Currently, I have fontconfig set up such that: $ fc-match :family=ui-monospace VeraMono.ttf: "Bitstream Vera Sans Mono" "Roman" $ fc-match :family=monospace VeraMono.ttf: "Bitstream Vera Sans Mono" "Roman" Firefox's fonts in about:preferences are configured as all defaults: Serif: Bitstream Vera Serif Sans: Bitstream Vera Sans Monospace: Bitstream Vera Sans Mono
첨부된 스크린샷

선택된 해결법

Turns out I was having a similar problem to this person, due to the fontconfig hackery of ttf-twemoji-color. I've removed that package for now and gotten everything rendering properly again!

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (1)

more options

선택된 해결법

Turns out I was having a similar problem to this person, due to the fontconfig hackery of ttf-twemoji-color. I've removed that package for now and gotten everything rendering properly again!