Closed
Bug 1373420
Opened 7 years ago
Closed 5 years ago
Use CSS variables for font-size and family; User Story and other textareas should be displayed in Fira Sans
Categories
(bugzilla.mozilla.org :: User Interface, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: emceeaich, Assigned: kohei)
References
Details
Attachments
(1 file, 1 obsolete file)
128.97 KB,
image/png
|
Details |
See screenshot. This is *not* related to bug 1369872.
Assignee | ||
Comment 1•7 years ago
|
||
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
Assignee | ||
Updated•6 years ago
|
Status: ASSIGNED → NEW
Assignee | ||
Updated•6 years ago
|
Attachment #8886234 -
Attachment is obsolete: true
Assignee | ||
Comment 2•6 years ago
|
||
I’ll revisit this once the Markdown support (Bug 1456878) is complete. We can use CSS variables for font-family, font-size and eventually everything else.
Status: NEW → ASSIGNED
See Also: → bmo-markdown-initial-release
Assignee | ||
Comment 3•6 years ago
|
||
Forgot to say: On some admin pages, <textarea>s are rendered in Courier, which has to be fixed as well.
Component: User Interface: Modal → User Interface
Summary: Font for User Story is Courier instead of Fira Sans → Use CSS variables for font-size and family; user story and textareas should be displayed in Fira Sans
Assignee | ||
Updated•6 years ago
|
Summary: Use CSS variables for font-size and family; user story and textareas should be displayed in Fira Sans → Use CSS variables for font-size and family; User Story and other textareas should be displayed in Fira Sans
Assignee | ||
Updated•6 years ago
|
Status: ASSIGNED → NEW
Depends on: bmo-markdown-initial-release
Assignee | ||
Updated•6 years ago
|
Blocks: bmo-edit-comments
Assignee | ||
Comment 4•6 years ago
|
||
I’ll do this as part of the upcoming design system work. (Bug 1377977)
No longer blocks: bmo-edit-comments
Status: NEW → RESOLVED
Closed: 6 years ago
No longer depends on: bmo-markdown-initial-release
Resolution: --- → WONTFIX
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Solved in Bug 1377977.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•