Web version displays italicized words as monospace, without italics
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- css
- Domain
- documentation
Research direction
Locate the #documentation #main p em CSS rule shown in the issue and inspect how it affects em elements in the HTML documentation. Adjust the styling so italicized terms render as italics rather than monospace, then compare the HTML examples with the PDF presentation.
Written by the indexing model from the issue text.
Description
Several jargon terms are marked with italics in the PDF version. For example, staged in section The Three States, or remote in section The Refspec.
In the HTML version though, these terms are <em> elements which are formatted as monospace rather than italics. This is due to the following CSS rule, which overrides UA stylesheets:
#documentation #main p em {
font-family: Courier,monospace !important;
font-variant-ligatures: none;
font-style: normal;
font-weight: 700;
color: #4e443c;
}
In several cases (jargon terms), it might be sensible to use monospace, but "disabling" italics seems misguided, making the format both less common and harder to distinguish from code fragments. For sure, the format would better be consistent regardless of the version.
- Dominant language
- CSS
- Stars
- 6.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from progit/progit2
-
Difficulty 1/5 Under an hour Newbie friendliness 87/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
AI-Agent/Queued Type/Bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
approved documentation
Difficulty 1/5 Under an hour Newbie friendliness 89/100
vitest-dev/vitest#12015 · 4 comments ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·