Closed WoodrowShigeru closed 2 years ago
I'm assuming you are using the github
parser? With the markdown
parser, it works fine, but with the github
parser it does not, but this is not a bug.
With the github
parser, we simply send it to GitHub via their API, let them process it, and send it back. If it is considered a problem at all, it is their problem.
To demonstrate, lets enter <u>cheesecake</u>
into this comment, which uses GitHub's parser, and see what happens!
cheesecake
Yep, no underline. Why do they ignore <u>
? 🤷🏻 You may want to consider <ins>cheesecake</ins>
instead.
cheesecake
I had actually checked the "github" and "gitlab" parsers – but not "markdown", because I could never see anything work there that the other two couldn't. Well, seems like I've found my first case.
Interesting! I did not know about <ins>
. What a weird choice by Chrome to underline that, even though "added text" has nothing to do with underlinage.
Thanks for the tips. Now I know not one but two workarounds. Cheers!
The HTML tag
<u>cheesecake</u>
is completely being ignored.Reproduce:
<u></u>
HTML tag.Sublime 4126 Ubuntu 18.04.6