Bug 283303
| Summary: | [Bugzilla] Use monospaced font | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Enrique Ocaña <eocanha> |
| Component: | WebKit Website | Assignee: | Enrique Ocaña <eocanha> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Enhancement | CC: | aperez, ap, jond |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=283301 | ||
Enrique Ocaña
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 | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Enrique Ocaña
Pull request: https://github.com/WebKit/WebKit/pull/36806
Enrique Ocaña
Possible duplicate of #283301.
Alexey Proskuryakov
I think that this should be solved by enabling Markdown.
Enrique Ocaña
```
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
Sorry for being unclear, I meant that we'd need to pick up the support from upstream first.
Enrique Ocaña
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
> 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
Closing this bug as wontfix (with this "always force monospace" approach, at least).
Thanks for the clarifications.