RESOLVED WONTFIX283303
[Bugzilla] Use monospaced font
https://bugs.webkit.org/show_bug.cgi?id=283303
Summary [Bugzilla] Use monospaced font
Enrique Ocaña
Reported 2024-11-18 09:46:36 PST
It's not uncommon for comments in bug reports to include pieces of code or other text-based content. An example of this is this is the file format dump in https://bugs.webkit.org/show_bug.cgi?id=254222. For this kind of content, it makes more sense to use monospaced font in comment text boxes, which was a feature available in the previous Bugzilla version. I understand that this is a matter of taste, and there's as many tastes as people. In case the team in charge of Bugzilla decides it doesn't make sense, I'd still like to link a custom Stylus stile that overrides that setting for those of us who prefer monospace no matter what: https://userstyles.world/style/19355/webkit-bugzilla-monospaced
Attachments
Enrique Ocaña
Comment 1 2024-11-18 09:51:16 PST
Enrique Ocaña
Comment 2 2024-11-18 09:55:58 PST
Possible duplicate of #283301.
Alexey Proskuryakov
Comment 3 2024-11-18 10:59:05 PST
I think that this should be solved by enabling Markdown.
Enrique Ocaña
Comment 4 2024-11-19 02:00:30 PST
``` Looks like it's not enabled by default and I couldn't see any option to enable it in the user preferences either. Is it something that an admin can enable? ```
Alexey Proskuryakov
Comment 5 2024-11-19 08:26:37 PST
Sorry for being unclear, I meant that we'd need to pick up the support from upstream first.
Enrique Ocaña
Comment 6 2024-11-20 01:35:06 PST
Ok. If you see (hopefully near-mid) future support of Markdown is the way to go, I think I can keep living with the Stylus hack in my local browser until then. Should I close this bug report?
Enrique Ocaña
Comment 7 2024-11-20 01:56:34 PST
> Should I close this bug report? In that case, please r- the Pull Request, because it's currently r+'d and I don't know what to do with it, as there are conflicting opinions.
Enrique Ocaña
Comment 8 2024-11-20 11:46:48 PST
Closing this bug as wontfix (with this "always force monospace" approach, at least). Thanks for the clarifications.
Note You need to log in before you can comment on or make changes to this bug.