Defect #20372
Contents inside <pre> are not rendered as monospace font in Chrome for Mac
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | % Done: | 0% | ||
Category: | UI | |||
Target version: | 3.1.0 | |||
Resolution: | Fixed | Affected version: |
Description
Although contents inside pre
elements are expected to be rendered as monospace font, but san-serif fonts are used for them when accessing Redmine with Chrome for Mac.
This can be fixed by setting CSS font-family.
current trunk:
A proportional font is used to show source code. 4 spaces indentation looks like 2 or 3 spaces. Undesirable.
with the patch:
Source code should be rendered like this.
This patch adds the following line to the stylesheet.
pre, code {font-family: Consolas, Menlo, "Liberation Mono", Courier, monospace;}
This covers many operating systems.
- Consolas: included with windows
- Menlo: included with Mac and iOS
- Liberation Mono: included with Ubuntu
Related issues
Associated revisions
Contents inside
are not rendered as monospace font in Chrome for Mac (#20372). Patch by Go MAEDA.
History
#1
Updated by Go MAEDA over 7 years ago
- Description updated (diff)
- Target version set to 3.1.0
Let's include this fix in the next release.
#2
Updated by Jean-Philippe Lang over 7 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Patch committed, thanks.
#3
Updated by Go MAEDA over 7 years ago
Thanks for merging!
#4
Updated by Go MAEDA over 7 years ago
- Related to Defect #20407: Monospace font-family values are differ between application.css and scm.css added
#5
Updated by Go MAEDA over 3 years ago
- Related to Defect #32170: Text enclosed in pre tag in Wiki formatting reference is not displayed in monospaced font in Chrome added