Note textarea font is no longer fixed width

Prior to 8.7 the font in the note/comment textarea was fixed width:

But has been changed in 8.7 to match the design mockups:

---

I think the textareas should always use a fixed width font.

mentioned in issue #14939 (closed)

I don't think they should have the mono space font. It looks so much nicer with the normal font.

I agree if it was always code, but the textarea isn't always for code.

So I'm a for this

I agree if it was always code, but the textarea isn't always for code.

Sure, but it is sometimes. We are a code review tool, after all, so I'd guess it's actually pretty often. And code always looks better with a fixed width font.

To me this looks really bad, for example:

cc @dzaporozhets @skyruler @DouweM

This is so unpleasant to work with!

Honestly - I prefer it. It looks so much nicer when typing out text, whereas the monospace font makes normal text look horrible.

Think we are going to need a decision from @skyruler?

@skyruler please decide if there will be monospace or regular font in comment form.

P.S. Although I work with code too I prefer regular font in comment area. It feels more human than typing something monospace which will be rendered as regular anyway in most cases

I'll just fix it with Stylebot.

Status changed to closed

@DouweM what you think?

@skyruler for the regular font. It looks prettier, and while it does look weird with code, the textarea is pretty bad for code editing anyway, since we don’t have auto indentation. I always write code in an editor and then copy paste, which is of course still possible now.

I have this crazy idea of using a contenteditable div instead of a textarea for our Markdown inputs, and automatically detecting code block boundaries in the entered text, and automatically wrapping them in a div with a monospace font while you're typing. We could do the same thing with things like _ and * to italicize and bold the text between the tags. It would basically be syntax highlighting inside a textarea like on https://jsbin.com/, but specifically for GitLab Flavored Markdown.

cc @jschatz1

Good idea @DouweM. contentedible is notoriously rough to deal with. But if you want we can check out stackoverflows editor. It's open source and does markdown really really well. I believe it's here https://github.com/derobins/wmd

@DouweM are you volunteering to develop it? I hate working with contenteditable.

@jschatz1 That doesn't appear to have the WYSIWYG quality I was hoping for, as far as I can see.

@connorshea If you are volunteering to clone me first, maybe we can get my clone to do it with all the free time he'll have. :) I may hack away at it some day, I like the challenge of taming contenteditable :D

@DouweM if this content editable thing is a ~Frontend thing why don't we make it an official issue and put it in the next/next next milestone?

@DouweM then it solved

@jschatz1 https://gitlab.com/gitlab-org/gitlab-ce/issues/15461

This has also made using ordered lists, bullet points, and task lists much less pleasant. Would #15461 (moved) improve that?

mentioned in issue #15461 (moved)

mentioned in issue #26236 (closed)

mentioned in issue #26709 (closed)