Hi Christian,
Normally I would post this as a separate issue (feature request), but it
could be technically related.
Would it be possible/feasible to switch to CommonMark?
We'd love to make better use of RB screen real estate in the Description
(we populate it by the API, and we put quite a lot
Unfortunately, not any time in the near future. The module we use for all
Markdown support doesn’t support CommonMark. It might be possible to extend
the support some, but it’s unlikely we can make that a priority on our
roadmap until Review Board 6 at this point, at the earliest.
If there are
Hi Christian, that's great news, since not rendering custom URL protocols
is the blocking issue for us.
Thanks for thinking along about CommonMark, I'm withdrawing that request
for now (I only mentioned it because of possible positive security related
side effects, next to enhanced markup,
Hi!
Long-ish timer user, first time bug-reporter. I'm using 3.0.14 so maybe
this is already fixed, in which case you can disregard.
I was writing a description that involved a string that had extra spaces in
the middle. I figured reviewboard would eat the extra spaces by default so
I decided
