<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "bug" label: - https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Checklist <!-- Please test the latest versions, that will remove the possibility that you see a bug that is fixed in a newer version. --> - [x] I'm using the latest version of the extension ([see the latest version in the right column of this page](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow)) - Extension version: v3.62.0 - [x] I'm using the latest VS Code version ([find the latest version here](https://github.com/microsoft/vscode/releases)) - VS Code version: 1.78.0 - [x] I'm using a supported version of GitLab ([see README for the supported version](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/README.md#minimum-supported-version)) - GitLab version: happens on `gitlab.com` ### Summary Markdown strikethrough is not rendered properly ### Steps to reproduce - Create a new MR - Edit the MR on gitlab.com and add a new line with `~something~` ### What is the current _bug_ behavior? Markdown is rendered as: \~strikethrough\~ ### What is the expected _correct_ behavior? Markdown should be rendered as: ~strikethrough~